>>Hi All,
>>
>>I need to export some records from multiple tables to a XML file, then import them to a SQL Server 7 database (using another standalone small app written in VB/VFP or whatever). The file can be saved to a floppy or sent by eMail to the central office where the SQL Server resides.
>>
>
>Is there a reason you specifically want to use XML?
>
>Are the source tables VFP tables?
>
>If the import program can be VFP, why not just use VFP tables? you don't even need offline views if you have control over server side processing. You can just write code to open and SCAN the tables, inserting each record in the the SQL database through SPT or remote view, or whatever.
>
>>I'm wondering if using XML will be a waste of time/effort, and if something else can be implemented instead (offline views??). (I tried once to export 3000+ records to XML using MSXML DOM, but the DOM is so sloooow to save/load.)
>
>You're right, XMLDOM is very slow when dealing with this many records, but then again, it's not really designed to do that.


Yes, the source tables are contained in a VFP DBC. I was concerned about records from multiple tables (just one file ala-MDB is good to handle by users), and also to preserve long fieldnames, etc.

I was thinking on relying on another XML parser without all that unnecessary complexity of the DOM methods/properties (still figuring out if the DOM is really needed. A set of \ , \\ and _PRETEXT lines do the job :-)), but I haven't heard of any).

It seems I'll keep my eyes on VFP as always, and forget XML for now. I really hated local views, powerful but troublemakers. Now I'm changing my mind after using remote views...

Thanks!

BTW, have you tried eXcelon Stylus for creating XSL templates? I looove it!
It's one of the first visual designers for XSL.
(We created another application written enterily in VFP, that saves the data in XML files, and renders it using XSL templates created with Stylus, using an integrated IE5 browser: very nice results!. But I'm still thinking the XSL is too difficult, the same for the DOM.)