It really depends...

First off, when you say VFP, do you mean:

1. VFP UI?
2. VFP COM Component?

Also, while my data is persisted on a SQL back-end, is that the only place to which I am passing data? For example, I might need to pass data to Excel.

Another concern is security. You may be mandated to use stored procedures. This will cut you off from remote views right away. I myself use SP's. And, if you have seen my other posts, I am not a fan of remote views.

However, in many cases, remote views offer a quick,and flexible way to work with back-end data. Even I cannot argue with that...

To me, the horse race is between ADO and SPT. SPT has the advantage in that data is already rendered as a VFP cursor. This feature is quite powerful. And, if I don't need to get data from a component, i.e., I am talking to the data source directly from the EXE, I would use SPT and stored procedures.. This scenario would not preclude my use of ADO in cases where I need to get data from my SQL backend, and then pass it off to an office/VBA application..

However, if I am getting data from components, for whatever reason, I would use ADO almost exclusively...

Not an easy question to answer...


>Assuming that you are using a SQL back-end DB, what is your prefered way to pass data to and from VFP?
>
>TIA.
>
>Peter Robinson