Be careful of memo fields. They are not compatible, and if you write to a memo field in VFP, FP2.6 will stumble on it when it gets to that record. Other records will still be OK, but anyone skipping through the records will hit a wall when the record pointer gets to that record. Errors will occur under other traversing circumstances, too.
Dana
>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).
Where's the damned Any Key?...too late