I too did find a work around for it... 1. In the client make a local copy of the Recordset, which I get from the middle-tier. 2. Delete the newly added record from the original Recordset. 3. Fill this Recordset to a Dataset. (Filling an empty Recordset works without any issues). 4. Insert a row into the newly gotten table of the Dataset. 5. Use the local copy and populate the default data of the new row. 6. Destroy the local Recordset copy.
This works perfectly fine. I am not messing around with any field attribute, no junk default values to not null fields and most importantly, Identity column's identity is maintained. But, I haven't tested the performance degrade(given my scenario, I don't think it will hit me badly). Note that in the first step above, you can not use, Clone. If you do that, when you delete the record from the original Recordset, record form cloned Recordset is also deleted. I used Recordset's Save to XML stream and open from XML stream capabilities. Curtis, I am also going to take a dig at your method and compare the two. I have a question. Did you have any identity column? If, yes didn't it give any problem (while Filling it and also while saving the data back to the database)? I don't see a reason to have any problem, just confirming it... Thanks for your inputs and thoughts Rathna Raj Icode -----Original Message----- From: Curtis Koppang [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Catch 22... (Recordset to Dataset issue...) Not sure if this helps, but I will toss it out there. We had a similar issue with Recordsets and trying to pass them around using a home grown web service. To work around the issue we would get the RS XML and modify the schema to take out the non-null stuff. Then pass it to the remote app who had no problem turning it back into a RS and partying on it. If you want more details, ping me. Later, curt You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
