John:

What I meant to say is that using remote VIEWS, you can work with SQL Server data with less hassel than the way I saw it demonstrated to me at a SQL Server Class using VB. With VIEWS, your update code, conflict resolution, batch processing, ect., is all taken care of for you using low-level VFP functions. You can bind your controls on the property sheet to the DE and off you go. The way they were teaching it in VB included hard coding SQL Updates and Inserts, hardcoding conflict resolution, binding form controls with code on the fly, ect. It was a ton of code! Although it may be more efficent to do it this way using disconnected data because it is less resource intensive on the client and you are not sustaining locks on the server, but isn't that ture only in a very high transaction environment? They also said that the bound control technique was really only good for prototyping. Now, I haven't heard that said about remote Views, which use bound controls.

Yes, I also think VFP is more flexible than ADO. With VFP you can subclass the cursor class and the DE to create custom data management classes. That opens a whole world of possiblities. Can you do that with ADO?

When I said native data access I meant that there were features built into the language for client server development. Your not instantiating a COM object for these services.

Finally, i know VFP is a file server database and not capable of processing data access tasks in a seperate process. You didn't have to acuse me of such ignorance.

Charlie