>Hi Jeff:
>
>>>Well, here is where we differ. In a client server environment you minimize the data brought across the wire.
>
>I agree with you on that point. I wasn't refering to bringing large amounts of data down the wire, that would negate the benefit of a client server applicaton. What I'm saying is Fox's relational commands can save you round trips to the server. For example, lets say you were working with invoices and each invoice has a few line items. Its nice to bring both the line items and the invoice detail at once, then relate the tables. Same goes static data, like pick lists that you can store in a VFP database locally on the client. Again, this saves round trips to the server.
>
>For reasons we have discussed I just don't see how ADO can be a better chioce for C\S app in VFP.
>
>Charlie

How about speed? I suppose your framework is built around VFP Cursors and it may be too much work but, if you are working with SQL Server the OLEDB provider is at least twice as fast as SPT with ODBC.

Just found out the hard way when I responded to John Koziol about SPT being faster (from previous ODBC tests of mine) when John Petersen corrected saying ADO and OLEDB provider is faster than SPT.