Hi John,


>Hi Benoit,
>
>The reason that it's so slow is that the application is not using "true" OLE DB access to the VFP data, it's using the ODBC provider for OLE DB and ODBC is slow. We won't get a native OLE DB provider for VFP data until VFP 7 is released.
>

Yes, that is what I explained to them. But since the response time is really a problem and they need a fix quickly, VFP OLE DB is not an option :).

>I don't think DataClas is going to help you. While it's an impressive product, it's mainly for simplifying and standarding data access and it's not going to alleviate the speed issue.
>

I see.

>If you have to use VB on the front-end, I would suggest that you migrate the back-end to either SQL Server or MSDE, depending on the scope of the application. You can then use ADO through the native SQL Server OLE DB provider and the application will be much, much faster. And there's where DataClas might help you.
>
>

To choose between MSDE and SQL Server... What should I look for?

>>I'm being ask to help someone with a problem and I'm looking for ideas, insights and workaround :-)
>>
>>An application is built with VB as frontend and connects through ADO to a VFP backend.
>>
>>The problem is that it is very slow (up to 20 seconds in some cases)when updating the database.
>>
>>I have work with VFP and with VB but never with this kind of setup and, before I diving in, I would welcome your comments.
>>
>>Some solutions come to mind, and would like your input, or other solutions :)
>>1. use of DataClass (I thought this would apply to VB/VFP apps)
>>2. migrate the backend to SQLServer (although VFP backend is fast)
>>3. migrate the frontend to VFP
>>
>>
>>TIA.