This project has moved. For the latest updates, please go here.


COM error when opening any mdb


on Windows 7 Ultimate x64
can provide more sysinfo if needed

file attachments

Closed Oct 14, 2011 at 7:51 AM by mnieto
Cannot reproduce. Plesase download last revisión (versión 1.5 beta)


mnieto wrote Apr 25, 2011 at 9:36 PM

Please, be sure that you have installed MS Office Primary Interop Assemblies (PIA modules) in your computer. You can install them during the Office installation (checking the option .NET compatibility for the diferent products of MS Office. Or you can download from Microsoft:

Please, give me feedback if this solution is correct or not.

best regards

onewinter wrote Apr 26, 2011 at 8:20 PM

unfortunately, installing the MS Office Primary Interop Assemblies does not help. I installed, then tried AccessSVN and got the same error as before. I also rebooted to ensure that had nothing to do with the problem, but I still got the same error message after a reboot.

mnieto wrote Apr 27, 2011 at 10:29 PM

Could be an issue with x64. In the next release I will target the application only for 32bits (in 64bits systems will run on WOW64):

Another workarround for the problem is:
copy the dll's in 'C:\Program Files\Common Files\microsoft shared\dao' to the directory where AccessScrCtrl.exe is.

onewinter wrote Apr 28, 2011 at 12:06 PM

i think you are right about the x64. i copied the dlls from the same path, except using Program Files (x86), as the path did not exist under the 64 bit Program Files... that did the trick. Thanks!

wrote May 6, 2011 at 4:03 PM

onewinter wrote May 6, 2011 at 4:03 PM

a follow up to this issue--adding the dlls to the correct directory let me open the mdb with accesssvn and view the different objects in the tree preview, however once i select an object(s) and hit save, i get an unhandled exception after it creates the Tables directory, but before saving any object definitions to disk.

i copied the actual debug output from the window and can provide that too, if needed.

mnieto wrote May 8, 2011 at 9:29 PM

please, copy the details text of the exception windows and send it as attached file. It would be nice if I could see the stack trace of the error.

wrote May 9, 2011 at 1:16 PM

onewinter wrote May 9, 2011 at 1:16 PM

stack trace attached

wrote Oct 14, 2011 at 7:51 AM

wrote Feb 14, 2013 at 6:33 PM

wrote May 16, 2013 at 8:53 AM