>>>>Just curious, why bother with ADO?
>>>
>>>Why bother with ODBC <g> ? I think ADO is a much better approach than ODBC for C/S apps. Obviously I'll accept suggestions on this too.
>>
>>Try using seek() on an Active data object... :)
>
>That's a good point but not a limitant. Maybe using ADO you have to change the way your programs are coded and get rid of some of the VFP data manipulation facilities but you has SQL/T-SQL to your disposition anyway, don't you? If I'm wrong with my point of view just let me know, as I said before I'm just giving my first footsteps on C/S programming and may have some misconceptions.
>
>Enmanuel

In a typical web app you would be pulling data from a data server to the web server on a web hit that generates some kind of report. If you use ADO on the web server side, like you would with ASP, you limit yourself to using stored procedures (T-Sql) on the data server and lose all the benefits of FoxPro. It's just more versatile to use VFP cursors, and you can still convert your FoxPro cursors to ADO if you want to utilize ASP. But frankly, VFP generated HTML is much faster than ASP using ADO. The same goes for desktop client/server environments.