The link which I have provided earlier is a very brilliant way of saving the DataSet (having multiple parent and child tables) using TableAdapters plus it also utilizes the Transactions. I suggest you all have a look at that. But that was about VS 2005.
On Thu, Feb 25, 2010 at 3:23 AM, Jamie Fraser <[email protected]>wrote: > The only solution I found, when using lots of nested datatables, was to > ditch them altogether and use pocos with some kind of persistence framework. > Yes, steeper learning curve, but much more flexible (and powerful) than > datasets. Also, imo, a much more natural way to work. > > -Jamie > > On 24 Feb 2010 17:42, "ThanderMaX" <[email protected]> wrote: > > @Doug : One helpful advise before you try to save whole Dataset full > of interrelated tables (with many foreign key constraints) , > > If you try to save it using cascade-update-delete and get transaction > error from deep within generated table adapter code , try disabling > the constraint before saving because it might issue constraint failure > due to nested table constraints. > > Also I have seen VS generated table adapter code to hang while > committing the transaction due to nested table constraints. > After a lot of debugging I found it tries to sort the constraints > according to hierarchy , for example Dataset with tables having more > than 2-3 foreign key constraints repeatedly hanged in that sorting > loop. > Still could not find any good solution to that problem , I had to > manually patch the code :( > > In the end, it all depends on you Dataset schema and relations. > > > Wish you good luck. > > > > > On Feb 24, 9:43 am, Arsalan Tamiz <[email protected]> wrote: > > http://blogs.msdn.com/bethmassi/archive/2007/07/11/tableadapters-and-... > > > > > On Feb 24, 2:04 am, "Charles A. Lopez" <[email protected]> > > wrote: > > > > > I've been away. ... > >
