Dave,
I don't know where you heard your information about the ODBC driver but it is out of date. The latest ODBC driver that comes with VFP 6 supports all triggers. It does not support stored procedure calls unless they are called by a trigger.

If that is the only thing holding you up, then I suggest you upgrade. The ODBC driver is very stable when used by ASP and the integration of Stonefield will help solve any problems you do have with corruption (which won't be that many).


>Currently a client has a Foxpro 2.6 for Windows application running. The application is stable. The .dbf files the application uses are also modified by an Active Server page via ODBC. The ODBC connections to the database are stable. Overall the client is happy with the stability of the database and the active server page.
>
>However, the client wants to move to VFP 6 with Stonefield Database toolkit and a "modern" VFP6 database. That is, a ".dbc" with triggers, cascading, and persistent relationships between tables.
>The problem is : ODBC does not support these activities. Thus, the ASP page accessing the data will not benefit from these enhancements only the Visual Foxpro application will benefit.
>
>My question : is ODBC stable when accessing VFP databases and tables that contain triggers, persistent relationships, and Stonefield?
>
>Is there a particular version of the ODBC driver that is recommended for VFP 6 databases using Stonefield?
>
>OR should I avoid the upgrade completely because ODBC will work properly?
>
>Although I will use an ODBC driver for VFP 6 databases I plan on treating the Foxpro ".dbf" files as though they do not have triggers or persistent relationships when dealing with them from the Active Server page.
>
>TIA