CursorAdapter allows much more flexibility. You can only call stored procedures using SPT and CA, not RVs. CA is the only method of the three that supports OLE DB, which will be faster and consume fewer resources than ODBC.
RVs are good for a quick-and-dirty conversion of a VFP app to client/server. Use them as a data source for a form or report.
SQL Pass-Through is my preferred method. It lets you do just about anything that can be done on the server, including running stored procedures, creating databases and tables, setting up user accounts, and so on (always subject to permissions, of course).
CursorAdapters are good in cases where you might want to switch to some other data source in future, such as XML. I haven't had much experience with them yet, but I'm sure I will use them more and more in future.
My advice would be to study all three methods, and use whichever one is appropriate in a given case. You might well end up using all three, which is fine.
I have to disagree here. ODBC, the basis for SPT and RVs is on the way out, being replaced by OLE DB. Don't get stuck in a situation where MS suddenly says they will no longer update the SQL Server ODBC driver and you have to make changes to your application on short notice.
Also, as I said earlier, OLE DB provides better performance over ODBC and uses fewer resources.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.