>Remote views are a great learning tool for client/server and often will get the job done. This is the easiest way to bind controls to data.
>

No they are not.. Rather, RV's buffer you from the details one needs to really know to do the job right....

Other than that, you post is fairly accurate...




>Use SPT if......
>
>You are dealing with large data sets, are comfortable with T-SQL, and/or have identity or uniqueidentifier fields defined in the SQL Server database.
>
>Use ADO if.....
>
>If this may be an n-tier solution involving non-VFP and non-SQL Server components. Since you can't directly bind controls to ADO recordsets, then you almost have to design your system similar to the old Fox way of using memvars or arrays for displaying and manipulating data. Then again, there are the VFPCOM functions for CursorToRs and RSToCursor to move data between tables and recordsets that may alleviate the binding issues....
>
>Conclusion:
>
>Use what is comfortable and what you believe represents the best fit with your application architecture.
>
>>We are using SQL Server as Back-end, VFP as Front-End. Which of the above mechanisms is the best one to manipulate data? What mechanism is best suite in a specific case?