Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Transactions
Message
From
29/07/2002 13:35:08
 
General information
Forum:
ASP.NET
Category:
ADO.NET
Title:
Miscellaneous
Thread ID:
00683519
Message ID:
00683619
Views:
42
One of the "gotchas" with bringing down multiple tables with one SP, is that the table names are *always* table, Table1, Table2, etc. and I haven't found any way around that. So, you have to have your DataSet tables named appropriately. But, since we use typed DataSets, it's no big deal ... we can name our tables however we want to in the typed DataSet and thus have meaningful names to access our tables with.

As I said previously with the updates, we have the "roll-your-own" approach ... setting the SqlCommand to the SP, adding the Parameters (PK's usually) and doing a ExecuteNonQuery() seems to cover all the bases.

~~Bonnie


>Yep, it works for me. I kept running into problems before. IAC, what if you have multiple tables in the dataset? How do you handle that as well as updates right now???
>
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform