I think I may have found an issue with 2.02.b10 when populating
TableAdapters with GUIDs. I'm using C#, VS2008 & can reproduce it 100% of
the time with .Net 2.0 & 3.5 current SP for both.

There is a dataset with 1 table, and 1 tableadapter. There is only a GUID
parameter.. If I select "preview data" using the TableAdapter context menu,
the data is returned properly.

If I use the same GUID in the following code snippet, I get the EDB error in
the subject line:
WindowsFormsApplication1.dsDemo dsTable1 = new dsDemo();

WindowsFormsApplication1.dsDemoTableAdapters.taDepts taDepts = new
WindowsFormsApplication1.dsDemoTableAdapters.taDepts();

taDepts.Fill(dsTable1.tDepts,System.Guid.NewGuid() );

It's acting as though something gets messed up between the C# code, the
tableadapter and the DB. I just came accross this when converting from
autoincrementing integers to GUIDs in the app.

Anyone ever come accross this, and if so ever find a work around by chance?
I'm dead without it working...



I'll also email you the app & DB Tim.



Thanks



jr

Just found a possible workaround though I'm not sure if it'll fully work as
an alternate or not because I have hundreds of code changes to make for
this.

By changing the parameter type from Guid to string and send the
Guid.tostring() for each table adapter the error does not occur. It also
returns the right data using the 'preview data' tableadapter context menu.


jr

James,

See my email reply.  It's most likely just a GUID conversion issue with the
generic Object value assignments.  I'll let you know what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com