>Hi all
>
>i have some question
>
>1. which technique is better to develop client server application with VFP SQL Passthrough(Remote Views) or ADO
>
>2. Wut are the merits and demerits of ADO with VFP
>
>3. VFPCOM Utility can be used for converting ADO Recordsets to VFP Cursors, so why not to USE ADODB
>
>4. How to get the User Names and Passwords from SQL server and hows to change the User ID and Password for SQL Server using VFP + ADO
>
>Regards

Hard to answer questions :)

1) No one of them could be said as superior to others under all aspects. I myself generally mix using them. ie: As need arises one piece of app might use RV while others are using SPT and ADO.

2) Generally it's harder to bind and work with ADO in VFP than others. If you're new to this you might even think there is no way to bind ADO.

3) If you'd have a need to convert recordset to VFP cursor and then back to recordset then it's not a good idea to use ADO (IMHO).

4) Use sp_ functions of SQL server (like sp_password, sp_addlogin).

With VFP8 and .NET answering above slightly changes. (ADO seems to be going away slowly and ADO.NET will be the replacement)
Within VFP8 CursorAdapter class, XML* class makes it fairly easy to work with either SPT or ADO using native controls.
In summary use whichever you can master best.
Cetin