I have many Access97 apps that link to FoxPro 2.6 dbf files. I now have to make it so that Access 2003 can use these Access97 apps (without changing the file format).
(The boss bought a new laptop w/Vista. Office97 will not run on Vista, so he put Office2003 on it. The rest of the company is still on Office97.)
I tried opening existing apps in Access 2003. When I do anything that uses those links to FoxPro2.6 dbf's, I get the "Could not find installable ISAM" error message. So I'm trying to create a new "TestOdbc.mdb" Access97 app that links to the FoxPro2.6 dbf's via ODBC (in hopes that Access2003 will like that).
Each time I try, I go thru a sequence where I select the Visual Foxpro ODBC driver. I then get a "Configure Connection" box (with "Free Table directory" marked), where I browse to the drive & directory containing the FoxPro dbf's. Under an "Options" button, there are also checkboxes for "Null", "Deleted", and "Fetch data in background" that are marked by default, and one for "Exclusive" that is greyed out.
I've tried leaving them all checked, and tried unchecking "Deleted". Either way, when I get to the next step and select certain dbf tables to link to, I get an error message saying: "Invalid field definition 'DELETED()' in definition of index or relationship."
The two tables where this has happened so far are two of the FoxPro tables I need to access most frequently. They both have cdx indexes, and I've been accessing them every day for years using the old (ISAM?) method.
(The ODBC driver I'm using is "c"\Windows\system32\vfpodbc.dll dated 12/7/1999. I've seen comments about using an OLE DB driver instead, but will Access97 (DAO) use that?)
Can someone tell me how to fix this? (I don't program in FoxPro. Someone else here does that. I'm the bookkeeper, & also work on Access97.)