Recent content by DDH

Solution... For some reason, MS Access does not like it when you create the 64-bit ODBC datasource through the Control Panel/Admin Tools and add WorkArounds2=8192 directly as a registry entry and then just try to use that datasource. Instead you need to create (or recreate) the ODBC datasource...

Yes, DSN is system DSN. I did try the combination you suggested and it still throws the same error. The access links have not yet been created, so nothing to recreate. It's when I'm trying to create the link that I hit the error. I can login and see the list of table names from which to...

64 bit Windows 7 Access 2013 11.3 install is 64 bit Registry entry is in HKEY_LOCAL_MACHINE -> SOFTWARE -> ODBC -> ODBC.INI -> Arlington (where Arlington is the datasource name)

I have read the article (and many others) suggested above. I have even read an article on the Progress site that shows all the possible values of WorkArounds and WorkArounds2 (and tried a few others, hoping for a miracle!). Again, that solution worked for the 10.x versions of the driver, but...

We have several MS Access databases connected to a system that runs Progress. We have recently upgraded the backend system and are trying to update our MS Access databases to link to the new tables. We have installed the OPenEdge 11.3 odbc drivers. We can connect and see the new list of...