>For our VFP applications that share tables with 2.6 applications, we keep the tables in the 2.6 format and use them as free tables (not in a DBC). VFP and 2.6 play well together, as long as you do not use VFP to alter the structure of the 2.6 tables (adding/deleting of fields, adding/deleting of indexes will alter the structure). VFP can insert, update, add, edit, delete, pack, zap, and reindex 2.6 tables without affecting the structure (and 2.6 compatibility).

I can add regular type fields (those not VFP specific like currency, integer, datetime, etc) using VFP and 2.6 has no problem still reading them.