Expand my Community achievements bar.

Issue with 32-bit Forms Designer, Preview PDF post 64-bit Office 365 Microsoft Access installation (previously 32-bit Office 2016)

Avatar

Level 1

Hello all, 

Prior to 64-bit Office 365 install, the ODBC Driver Manger showed 32-bit drivers and connections to 32-bit Access Database worked flawlessly when using Forms Designer to preview PDFs.  After the 64-bit Office was installed, the Administrative Tools for ODBC Data Source Administrator (32-bit), User DSN tab, User Data Sources only show Excel Files and MS Access Database (mdb and accdb) 64-bit Drivers, and the window displays, "The driver of this User DSN only has a 64-bit version available. It can only be removed or configured with the 64-bit ODBC Data Source Administrator". 

We then installed the 32-bit version of 2016 Microsoft Access Database Engine Redistributable and the 32-bit drivers repopulated.  The issue we are having now is that when we attempt to use Designer and choose Preview PDF, we see the following error.  

Title: Adobe Acrobat
connect operation failed. [Microsoft] [ODBC Microsoft Access Driver] Could not use '(unknown)'; file already in use.  


When we monitor the folder where the database resides, we see it creates a lock file (.laccdb), which does not disappear until we close Designer. 

Does anyone know how to fix this issue?

2 Replies

Avatar

Level 1

Forgot to mention, the PDF form links to an .accdb that only has tables.  The original .accdb file was created in Access (32-bit), however in Access, the only thing we see is Dataset_1.  Normally, i would have checked to make sure Ptr and LongPtr Declarations were replaced, but this is only a Table with no Declarations. 

jwduncan_0-1667419256215.png

 

Avatar

Level 1

On second look the Access lock file appears when the Protected View warning pops up after opening the PDF Preview in Designer. Unfortunately, I do not have access to change the Trusted Locations and Protected View is a group policy so I cannot test this theory.  The files are on C: drive.  I even added the driver to System DSN to see if that would make a difference and it was same issue.