Hi Gary,
If you're referring to the issue here:
#TableAdapter generates bad SQL in dotnet.framework.adonet
http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.publi
c.dotnet.framework.adonet&tid=9db42ef6-ce06-42a0-8a17-d7c42e213c96&lang=en&c
r=US&m=1&p=1
My colleague Kevin mentioned that it's reported on the connect side as:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac
kID=111156
Here's the response by our product team:
-------------
Hi Diego, I took a look at this issue and it boils down to some confusion
regarding the TableAdapters and how ObjectDataSource works. To get this
scenario to work, you just have to perform two additional steps:
1. In your web project, click on the ObjectDataSource, and in the property
grid set its ConflictDetection property to CompareAllValues. The is
required because DataSets use optimistic concurrency for their methods.
2. In the GridView control, open the Smart Tag and click Edit Columns. In
the lower listbox ("Selected fields") select the OrderID column (because it
is the primary key), and reset its ReadOnly property back to False. This is
required because the DataSets are generated with an updatable primary key,
and the GridView doesn't realize that.
In future versions we hope to make this process a bit easier.
--------------
It's closed by "By Design", I'm afraid it's not addressed in SP1.
For a complete list of fix of Visual Studio 2005 SP1:
#List of bugs that are fixed in Visual Studio 2005 Service Pack 1
http://support.microsoft.com/default.aspx/kb/918526
Hope this helps.
Regards,
Walter Wang (
[email protected], remove 'online.')
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.