Hello all,

I'm working on a smart client application for my company. The client
uses .NET 2.0 typed datasets to store it's data. It works both in
'online' and 'offline' mode. When the application starts in online
mode it gets a new dataset diffgram from a web service. When it shuts
down in online mode it sends the changes made to the dataset to the
server and gets a new dataset. In offline mode it, when shutdown,
persists the typed dataset to disk as encrypted XML. The next time the
application starts it reads, decrypts, and sends any pre-existing
changes to the server and gets a new dataset.

My problem:
If there are schema changes made to the typed dataset in, say, version
2.0 it may make the locally persisted dataset written in version 1.9
unable to be loaded into the new version and data could be lost.

Because losing data is totally unacceptable to the business in this
case, I've got to find a way to load that older version's dataset and
then convert it to the new version then send it to the server as the
new version's type.

Any ideas on typed dataset versioning?


Thanks for your help,
Scott R. Jones
Coventry Health Care,
sxjones2NOSPAM@cvtIXNAYONTHESPAMAYy.com

prompt user to select from recordset.
Large VB ADO.NET Recordset Import into Excel
Better way for dropdownlists
Reading a SQLCLR Stored Proc. Result
Add Records