Backward Compatibility

  • Thread starter Thread starter Matt
  • Start date Start date
M

Matt

Look out! dotNet newbie coming through.

I really like the new DataSets available in ADO.NET and i understand that
they replace RecordSets for a number of reasons. Is there any backward
compatibility though? An XML transform that converts a DataSet to a
RecordSet?

I have a Client App on a COM platform that currently gets data from a Web
Server. The Web Server sends a disconnected RecordSet to the client rendered
as XML. The client then works with the RecordSet and in some cases updates
the RecordSet and sends it back to the server. Think pre-dotNet web service.

I would like this same Client App to (with the flick of a switch) talk to
both the old pre-dotNet service and a new dotNet WebService. The only way i
can think of doing this is to define my own proprietary XML language and
make both server platforms spit it out. This could take some time (the
client app has lots of RecordSet manipulation code in it).

Surely there is some way of EASILY making a WebServices return a RecordSet,
or make a ASP page return a DataSet?

Thanks,
Matt
 
You can work with ADO Recordsets easily in .NET, either directly or
with the XML files generated by saving ADO Recordsets by using COM
Interop. There is no need to define your own XML language. You might
want to get a good book on the subject, like David Sceppa's "ADO.NET"
published by Microsoft press.

-- Mary
MCW Technologies
http://www.mcwtech.com
 
Did you know there are WriteXML() and ReadXML() methods on a DataSet? That
may be all you need.
 
I'm not sure what the ADO generated XML looks like. How is it any
different? Xml is Xml. Any application that outputs XML should be
following the standard. With ADO.NET's DataSet, schema can either be
included in the Xml or be inferred from the data as it is read in.
 
Back
Top