Home/ Questions/Q 8879933
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T20:03:43+00:00

I have these error messages when I start MS-Access application (has VBA code). When

  • 0

I have these error messages when I start MS-Access application (has VBA code).

When I click OK in the first error message and debug in the second, the debugger opens up and points to the line that says: “Set oServer = New SQLDMO.SQLServer“

I realise that it’s a problem with SQL-DMO, but can’t seem to register the DLL.

My environment: Win7 Pro 64-bit, Office 2010 64-bit, MS SQL Server 2008 R2 SP2 64-bit.

I downloaded the backwards compatibility package from Microsoft, ran the MSI, and nothing.
Tried to manually install, and get error messages:

  1. R6034 for C:\Windows\System32\regsvr32.exe and when I click Ok –> The module “SQLDMO.DLL” failed to load. Make sure the binary is stored at the specified path or debug it… blah blah
  2. When I try to register it from C:\Windows\SysWOW64, I get “The module "SQLDMO.DLL" may not (be) compatible with the version of Windows that you're running. Check if the module is compatible with....

I’ve checked the version of SQLDMO.DLL and it is definitely 64-bit. I have located all the other DLLs that SQL-DMO needs and stored them in SysWOW64 and System32.

I have run Office repair, Windows Update, SQL Server repair (the log file indicates pass for everything for Client Tools Backwards Compatibility).

Any help is much appreciated.
Thanks, Miki.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Not sure how I’ve managed to, but have (somehow) managed to register the 64-bit SQLDMO.DLL (before it didn’t really register it) and then in my VBA code–> Tools –> References… I tried to load the SQLDMO.DLL from the 64-bit folder.
    At first, it didn’t work, and then I placed a copy of the DLL in SysWOW64 (which is a 32-bit folder) and registered it from there (once it was registered, apparently, the system doesn’t need it there anymore – I removed it, and it still works).
    I then tried to figure how come it works. I checked in the Reference Table in the VBA Code, and the Microsoft SQLDMO Object Library is still pointing to C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn, but when I removed SQLDMO.DLL from there it still worked… I then looked in C:\Program Files\Microsoft SQL Server\80\Tools\Binn and removed SQLDMO.DLL from there and then it stopped working!
    I have no idea what happened, or why the reference table is saying it’s pointing to one folder but actually pointing to a different one, or how after the same tries before, only now it works.
    I’d like to be able to replicate this (in case I need to go through this process again), so any ideas/suggestions would be greatly appreciated.
    Thanks, Miki.

    • 0