Go into VFP and modify the offending indexes to get rid of the DELETED() function, if you can. I'm not familiar enough with Access to address the other issue and I haven't yet worked with the VFP6 ODBC drivers....

Here's a thought: Why not set up a DSN for each table via the regular old FoxPro (*.dbf) driver? The index won't even be looked at that way.


>>You can't have a VFP function in an index and have that index be translated
>How do I stop Access from translating the index? I didn't see any options for that.
>
>>btw, which base ODBC driver are you using?
>MS VFP Driver 6.00.816700 (vfpodbc.dll) Visual FoxPro database (.dbc)
>Is that what you mean?
>
>TIA