I think the second question: "there's no equivalent to dynamic recordsets in ADO" is still to be solved. He means that there is no equivalent in a VFP remote view or SPT cursor to an ADO dynamic recordset. Perhaps someone has 'emulated' the dynamic recordset behavior.


>>Since I'm programmer here at Silogic, I tell my boss that programming in VB on SQL Server Database is more "standard" and more reliable than programming in VFP on VFP databases as we do. I think that each user opening directly tables on the file server, modify them, than closing them is not really secure and could dammage the database in case of a crash or something like that. In the last month, I made tests using SQL server and VB. I tried ADO, but I can't find any grid that works in VFP and is as flexible as VFP grid. I tried SQL pass-through to realize (today) that there's no equivalent to dynamic recordsets in ADO. My tests make me realize that the solution we have (working directly on the tables using native VFP database access) give us the most performance as is a lot more flexible (like using grids on large tables an keep them current). Now I believe that VFP is better designed for database solutions than VB, but what do you experienced VFP developpers think about working
>>directly on vfp tables Vs working with an SQL server ?
>>
>>Any comments, hint, advice, example, link or reference are welcome !
>>
>>Thanks a lot in advance !