Sign in | Join
Last post 07-04-2009 9:15 PM by malcolms. 4 replies.
Sort Posts: Oldest to newest Newest to oldest
Why is it complaining about something that isn't there? Yesterday it was working, today nothing changed and it's not working.
Complaing about non-nullable datatype, but all fields are set to zero (0)
So annoying! Ahh..
You're probably just letting out steam, but I'll bite. Is it working for you now, or do you have some code to show and possibly the exact error message?
Hey I think LINQ is a great technology! It means you can use it to query a bunch of stuff without having to know anything about each technology.
Okay onto your problem. Did you see a detailed error message? Did you check that the underlying database hasn't changed? If it has you'll need to manually refresh your dbml file.
Haha.. :) Yes, I was letting out steam.
It's more of ongoing weak database error messages, plus strange support for different datatypes between Linq and Sql Server.
Thanks for understanding :)
No worries! If you have more issues let us know.
Also Microsoft have created the Entity Framework as a successor to LINQ to SQL. You may want to look at that as a possible option.