Generally, you want to avoid ADO unless you have a specific purpose for it. If you're from the VB world, using ADO and creating objects with properties for each field is second nature, but in VFP, it's just extra overhead.
If your app will be converted to a SQL backend, check out remote views and SQL passthrough. They basically turn remote data into VFP tables and cursors so there is no need to use ADO.
I use ADO a fair amount in COM objects running under COM+ and MTS, but only to return data to VB or ASP clients.
Mike
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only