Share via

Error loading DLL whenever query/report wizard is used in access 2007

Anonymous
2012-02-20T23:18:51+00:00

I have started getting the following error:

'Error loading DLL'

Every time I try to use the query or report wizard in Access 2007. I am sure it is not the file as I can use it on other computers. I tried to repair and reinstall access but neither worked. I also tried to register Dao360 and Msado15  but this made no difference, I may have cheated on this though I found these files and right clicked and registered instead of using regsvr32.exe.

Can anyone help?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2012-02-21T14:51:00+00:00

    Hi Jamie,

    If you are on a 64 bit machine, you could try going through the steps in the KB article below.  If you don’t feel comfortable with editing the registry, then I would recommend creating a case with Microsoft so we can go through the issue with you.

    2019235 - Microsoft Office Access: "Error in loading dll"

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;2019235

    Online Assisted Support Options (create cases online) - http://support.microsoft.com/select/default.aspx?target=assistance

    This article covers 32 bit and 64 bit versions of Access, 32 bit and 64 bit operating systems, and also Access 2007 and 2010.  Because it covers all of these scenarios, you will need to ensure you use the correct steps and substitute the correct version of Office into the registry text.  If you are using Office 2007 on a 64 bit machine, you would want to do the following:

    Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

    1.     Open Notepad

    2.     Copy and paste the following lines of text for your environment, starting with 'Windows Registry Editor Version 5.00', into the Notepad document:

    (OS: 64bit Office: 32bit)

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\TypeLib{00025E01-0000-0000-C000-000000000046}\5.0\0\win32]

    @=hex(2):25,00,43,00,6f,00,6d,00,6d,00,6f,00,6e,00,50,00,72,00,6f,00,67,00,72,\

      00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,28,00,78,00,38,00,36,00,29,00,\

      25,00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,20,00,53,\

      00,68,00,61,00,72,00,65,00,64,00,5c,00,44,00,41,00,4f,00,5c,00,64,00,61,00,\

      6f,00,33,00,36,00,30,00,2e,00,64,00,6c,00,6c,00,00,00

    [HKEY_CLASSES_ROOT\TypeLib{4AC9E1DA-5BAD-4AC7-86E3-24F4CDCECA28}\c.0\0\win32]

    @="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\ACEDAO.DLL"

    3.     Save the Notepad file as Win32Keys.reg

    4.     Using Windows Explorer, navigate to C:\Windows\SysWow64\regedt32.exe and double-click on regedt32.exe to run it.

    5.     In the registry editor go to File > Import and browse to where you saved the Win32Keys.reg file, and then click Open.

    Hope that helps.

    Best Regards,

    Nathan O.

    Microsoft Online Community Support

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2013-05-14T09:20:56+00:00

    Thanks you so much . It worked for me like a cake.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-02-22T01:24:43+00:00

    Thanks Nathan,

    I had tried this fix previously and it didn't work, Sorry I forgot to mention it. I was on a fairly tight deadline and ended up reinstalling windows, I had started getting errors all over windows so it was going to have to happen sooner or later anyway.

    Thanks again for your reply,

    Jamie

    Was this answer helpful?

    0 comments No comments