>>If you really want a guarantee, try reading and writing to the FPW 2.6 tables through ODBC. Treat it like you would any other non-VFP data source.
>
>Won't that slow things down? How much of a performance hit do you take?

You would take the same performance hit as would with any other ODBC data source...which is to say, quite a bit. However, after repeated attempts to read a FP 2.6 table with VFP 5.0 and having the table auomatically convert itself to a VFP table, I discovered that ODBC was the only option.

How much access are doing of the FP 2.6 table? If it is fairly static, you might want to read it into a Remote view. That way, you read it in once, and then can read it like any other VFP table or view. Updating the FP 2.6 table may be a little trickier. SQL Pass-Through is much slower, but it is the only reliable way to have real-time data updates. (If I am wrong about this, somebody please let me know)

I will admit, I tend to shy away from ODBC in VFP, just for this reason. VFP is a speed demon when it comes to reading it's own data, but not so with other databases.

Bill