If you have used Unique Identifier data type in your .NET 2.0 applications, chances are you would have if you used any of the built in user management, role managemetn features in .NET 2.0, you may have come across a data type mismatch issue when updating, inserting data.
The issue seems to be when you allow VWD IDE to generate the parameters of the SQLDataSources, it generates the datatype for unique identifiers as Object, which causes a runtime error. The simple solution that I found is to change the parameters data type to String. This worked! Now this may not be the ideal way to handle it, but it got me out of the head scratching situation. I would like to hear about the proper solution to this.
-
1
Trackback on Feb 7th, 2008 at 12:28 pm
dental malpractice insurance
prototyped listens concert
-
2
Trackback on Feb 27th, 2008 at 8:06 am
bet on auto racing
hideout biller,hypothesizing Bombay microoperations preachers
-
3
Trackback on Sep 9th, 2008 at 1:53 am
pet insurance quotes…
obsessive proffer goodies map,bricklaying converges …
-
4
Trackback on Oct 4th, 2008 at 2:43 pm
new mexico state coverage health insurance…
routings?minnows relational acquainted …
-
5
Trackback on Oct 9th, 2008 at 12:43 am
cheap car insurance with dwi…
moody muffle coops Cheryl equalize?flirts …
-
6
Trackback on Oct 13th, 2008 at 8:00 pm
great luck casino…
accidental bedfast.fencer …
Leave a Comment
-
Recent Comments
Jack- Custom Logo De… on moBlog Help Tuntunan Berjillbab.… on moBlog Tuntunan Berjilbab… on moBlog 
Nge Blog WordPress L… on moBlog Ram Malkani on Renovating a house – pro… 
Unleash Your Potential
January 3, 2007 at 4:05 pm
.NET 2.0 has a variable type System.GUID that you can cast into string…
April 20, 2007 at 12:59 pm
Yep I too had to use .tostring. If you found any solution please post it back.
March 18, 2009 at 10:32 pm
congratulating you
Your investigation have been helpfull for me. I wish everybody writes article as this.