Prior to upgrading to Office 2013 I was able to successfully connect MS Access 2003 (on XP)  to my Advantage Database using the ODBC driver supplied by Advantage (Sybase) and creating a DSN in Windows. Subsequent to upgrading I have been unable to get this to work with O365 Access, having tried multiple approaches (different ODBC versions, 32 vs 64 bit ODBC installs, creating the DSN via Access External Data rather than via Windows control panel, creating a User DSN as well as System DSN, etc). I always get to a point where Access is correctly displaying all the tables in the Advantage database, but as soon as I select one of these tables to link to, the message "The Microsoft Access database engine could not find the object 'xxxxxx'. Make sure the objects exists ..." is displayed in a error popup. As I say, this is after Access has actually displayed the table object in a list for selection, proving that it is able to "see" the table via the ODBC connection.

Having struggled with this problem for a number of days now, I would really appreciate any assistance or suggestions. I am running Windows 7 and MS Office 2013 (Office 365 Home).

Have solved the issue. It happens because the collation sequence of the table is different to that expected by Access (based on the adslocal.cfg file settings being used by the ODBC driver). Once the adslocal.cfg is aligned to the collation sequence settings that the table was created with, the tabl can be linked in Access.

• Marked as answer by ClivePoorter 11 hours 3 minutes ago