We've successfully run MS Access (2003) for years against an accounting system whose files are stored in FoxPro 3.0 format (using a *.DBC - database container). Some payroll history tables have grown quite large, and now MS Access returns an "invalid index" error message from the ODBC driver. The same table/index for other 'divisions' within the payroll system still open fine. It seems that just the divisions with over about 250MB-sized compound index files (CDXs) are effected.
Other than removing older data, does anyone know of a workaround or fix ?