Hi Mike,
    The reason we are using XML to transport data is we are transferring lot 
of data from 1 application to another. That is the only way we can transfer 
data. My problem is if there are a lot of records (and there are) this 
process of traversing the dataset (datareader) and filling the class and 
serializing the data would take a long time. Is there any other process to do 
this?
Thanks,
Nagendra

"Mike Collier  AdoAnywhere" wrote:

> Error while executing SP <ErrorwhileexecutingSP@d...> wrote in message news:<4FB4A3DC-C397-4F4B-B47B-CB7D73EAAEBF@m...>...
> > I am trying to generate an xml file conforming to the xsd. My problem is the 
> > data is coming form the database. I have generated the clssses from the xsd. 
> > What is the best approach to generate the xml.
> > If I loop thorough the records from the database (there could be 20,000) 
> > then it will be very slow to fill the classes and serialize the class.
> > Is there any other way to do this? 
> > Thanks for the help.
> 
> Without knowing your exact design requirements I can't be specific:
> 
> My applciations are mostly 3 - tier.
> 
> I generate XML directly from recordsets, but I design my applications
> to select the minimum amount of data in the first place (about as much
> as a person can read in a grid). Never use "select * from table".
> 
> I then implement paging if necessary (say 20 rows at a a time). This
> can be  optimised in various ways.
> 
> If 20,000 records were needed then for me this would be for some kind
> of batch process and I would run this on a server without XML.
> 
> You can try xml & paging your own database by using the generic SOAP
> server from adoanywhere www.adoanywhere.com. It will give you some
> idea how long it takes to transform your data to XML and XSD. The
> paging is not currently optimised.
> 
> 
> Hope this helps , Mike.
>