>You have to remember these problems aren't VFP's problems - they're ADO
>problems for being so slow with COM access. If you did the same thing in
>VB using native ADO to dump to whatever format you'd have exactly the
>same issues!

Yeah, probably would save a few mSecs in the loops since VB is compiled. Not sure if ADO COM access is slow, guess it depends on what you compare it to. I've found that all COM access is rather slow.

>You have to weigh the convenience against the performance tradeoff.

>If performance is that big of an issue then maybe you have to look into
>using ADO front to end instead of converting back to VFP data natively,
>or else using ODBC. IOW, you can only do what the technology allows you
>to do.

Fine until record level processing is required, then you're hosed due to the speed problem. I'm keeping my fingers crossed that the ODBC option will become available and I can drop the ADO interface. It depends on the requirments of the application. In many cases the ODBC memory leak problem is acceptable.

>I think it's a good ER though to have ADO export to a some standard
>format that could be universally imported. Question is what format
>would that be??? Memos, binary data would be lost and it wouldn't
>solve all problems either. I guess XML exports will
>serve that in the future, but I doubt this will be terribly efficient
>either.

If the export function was built into ADO I see no reason why it would not be fast; relatively speaking, of course I felt the VFPCOM converter should have been fast too. The loss of memo and binary data is an issue but you have the same problem with VFP's export, an issue I could live with.

Thanks for the insight Rick, you have always been of help and a fantastic resource. Off topic a bit, have you played with the latest release of IIS's scripting engine? They finally added the "With" statement and a new "Class" statement to VBScript. Using Class in conjunction with remote scripting now allows Vbscript functions on the server side to be called directly by the client.

Best Regards,
Mike