Access 2007 Error in Loading DLL Revisited

[Sergio Torres]

I have MS Office Enterprise 2007 (12.0.6514.5000) SP2 MSO (12.0.6251.5000) on
a Windows 7 Ultimate 64 bits.

When I open the linked table manager in MS Access and try to check any
table I get an error message saying "The expression FldListCheckItem you
entered as the event property setting produced the following error: error in
loading dll."

There is no way for the OK button the get enabled, so I cannot use the
linked table manager.

If I try to use the Report or Query Wizards I get, twice, a msgbox saying
"Error in loading DLL" before the wizards opens. I haven't tried the wizards
after the messages.

I tried registering dao360.dll and msado15.dll with regsrv.exe... I received
a message saying they were registered, but the problem persists.

I ran the MS Office Diagnostincs and it found no problem.

I uninstalled office and installed it again. The problem is still there.

I checked and there are no pending updates.

Any ideas?

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[John W. Vinson]

In my PC, if I try to edit a piece of code in VBA editor window and write,
let's say, "Dim db as ". As soon as I press the space bar after the "as"
keyword, MS Access crashes and I get a msgbox saying: "Microsoft Office
Access has stopped working".

The references in the VBA editor window are:
Visual Basic For Applications
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft Access 12.0 Access database engine Object Library
Microsoft Windows Common Controls 6.0 (SP6)
Microsoft ActiveX Data Objects 2.7 Library.

Try removing the last two. Do you still crash on open? If not, can you
compile? Are you in fact *using* ADO or any Common Controls, and if so can you
find an alternative?

 

[Sergio Torres]

Thank you for your answer.

If you don't mind I rather stick to the Linked Table Manager and Report and
Query Wizards problem.

One way or another I managed to put to work the upgraded Access 2000
application (using its owner PC).

I created a new MS Access 2007 database.

I added a table to it and linked some tables from "Charitable
contributions.accdb" (a database created from a MS Access Template).

The report and query wizards behavior is the same, they produce the "error
in loading DLL" every time I select an option inside the wizards.

In the end reports and queries seems to be created.

The Linked Table Manager does not work at all.
a) If I click the "Select All" button, the Ok. stays disabled (even if I
check the "Always prompt for new location" option).

b) If I check any of the existing linked tables, I get the error message
"The expression FldListCheckItem you entered as the event property setting
produced the following error:Error in loading DLL".

As I said before, I registered dao360.dll and msado15.dll and the problem
persists.

I would really appreciate any help here.

Sergio

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[Sergio Torres]

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[David W. Fenton]

=?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?=

As I said before, I registered dao360.dll and msado15.dll and the
problem persists.

DAO 3.6 has nothing to do with A2007, nor does ADO 1.5. In general,
creating a reference to a library in Access will register it if it's
not already registered, but if you aren't using the reference, then
Access doesn't need the library to be registered.

 

[David W. Fenton]

Try removing the last two.

I would remove the OLE Automation reference, too. If you look at it
in the object browser, there's hardly anything of use in it, and I
don't understand at all why it is a default reference.

 

[Maurice]

It looks like the dll is damaged. Try running the repair option from the
about menu (menuoption - about - repair)

Backup db just to be sure!

 

[Sergio Torres]

David,

Thank you for taking the time to comment on my problem.

I mentioned registering dao360.dll and msado15.dll because there are several
articles stating that doing so solved the problem with the report and query
wizards, as well as with the linked table manager.

In my case, it did not help.

I am still experiencing the anoying "error in loading DLL" message and my
linked tables manager dos not work.
--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[Sergio Torres]

Maurice,

Thank you for your answer.

I am not sure I understand your suggestion. Are you talking about the
"Compact and Repair Database" option?

Although the database I am working with is brand new I tried that and the
problem persists.

Sergio
--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[David W. Fenton]

=?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?=

I mentioned registering dao360.dll and msado15.dll because there
are several articles stating that doing so solved the problem with
the report and query wizards, as well as with the linked table
manager.

Sounds like very old instructions. DAO 3.6 would apply to A2000
through 2003, but not A2007, and ADO 1.5 has never applied to any
version of Access -- when ADO was first introducted to Access in
A2000, it was up to version 2.1, if I'm remembering correctly.

In my case, it did not help.

I'm quite puzzled by the recommendation to re-register ADO 1.5, as
it shouldn't have any relationship to any of the Access wizards
unless it was being used as a reference.

I am still experiencing the anoying "error in loading DLL" message
and my linked tables manager dos not work.

Is the error specific to a particular database or do you get it if
you create a new blank database, link tables, and then try to use
the linked tables manager?

If it's not specific to a particular database, or you've cleaned out
all the references in your database and it still happens, I think
I'd try repairing the Office installation, and if that doesn't work,
uninstall/reinstall Office.

Also, if you have more than one version of Office/Access installed,
you might try running the non-2007 version, to let it configure
itself, then re-running A2007 to configure itself.

Let us know your results.

 

[Sergio Torres]

David,

The problem with the wizards and the linked table manager is database
independent. It happens always, even with newly created databases.

I already tried Repairing MS Office installation and I already tried
unistalling-reinstalling MS Office 2007.

My guess is that it is an Access bug that has to do with the 64 bits OS.


--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[David W. Fenton]

=?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?=

The problem with the wizards and the linked table manager is
database independent. It happens always, even with newly created
databases.

I already tried Repairing MS Office installation and I already
tried unistalling-reinstalling MS Office 2007.

My guess is that it is an Access bug that has to do with the 64
bits OS.

That shouldn't cause a problem.

Have you eliminated UAC as a source of the problem? That is, you
might need to set your Access shortcut to run as administrator.

 

[Sergio Torres]

David,

I followed your advise and checked the UAC option:

I:
Opened access as administrator.
Created a new database (2007 format).
Linked some tables to it.
Tried to use the Linked Tables manager (LTB). It didn't work.
Tried to use the Report and Query wiards. The "error in loading dll" message
appeared.

Changed UAC settings to disable it.
Restarted my PC.
Tried the previous process.
I got te same result.

Checked the Trust Center Settings.
Trusted Locations include the access default location for wizards databases.
Add-ins are enabled.
Macros are all enabled.

Added the following to the trusted locations:
The folder were the new databases are created (My Documents).
The folder where the back end databases exist.
The folder where the ado360.dll exists.
The folders where the msado15.dll exists.

Tried again, the problem persists.

Ran the MS Office Diagnostics (again) and got:
Check for known solutions — No issues found
Memory Diagnostic — No problems found
Update Diagnostic — No problems found
Compatibility Diagnostic — No problems found
Disk Diagnostic — No problems found
Setup Diagnostic — No problems found

What else can we try?

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[David W. Fenton]

=?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?=

What else can we try?

I don't know! The DLL error makes it seem like there's something
wrong with your Access installation.

One thing to try is to get the SysInternals Process Monitor and
filtering its results for every RESULT that's not SUCCESS. That
might turn up a missing component.

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

You would then want to check the same thing (for the DLL that turns
up not being found) on a machine where the linked-table manager
works.

I'm basicaly out of ideas at this point, though. All I can think of
is that your machine's NTFS permissions are set to something other
than the default permissions.

 

[Sergio Torres]

David,

I ran the sysinternals process monitor and got the following when I click
the checkbox selector inside the linked tables manager:

Access tries to "QueryOpen" dao360.dll in several locations:

C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll
C:\Users\Sergio\Documents\dao360.dll
C:\Windows\SysWOW64\dao360.dll
C:\Windows\system\dao360.dll
C:\Windows\dao360.dll
C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll
C:\Windows\SysWOW64\dao360.dll
C:\Windows\dao360.dll
C:\Windows\SysWOW64\wbem\dao360.dll
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\dao360.dll
C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\dao360.dll
C:\Users\Sergio\Documents\dao360.dll

and allways gets the result "FAST IO IS DISABLED".

After each "QueryOpen" it tries to "CreateFile" dao360.dll in the same
locations and always gets the result "Name Not Found".

The only location in my PC where dao360.dll exists is C:\Program Files
(x86)\Common Files\microsoft shared\DAO

The other entry that stands out is it tries to CreateFile C:\Program Files
(x86)\Microsoft Office\Office12\MSACC.OLB and treats it as a folder: tries to
CreateFile C:\Program Files (x86)\Microsoft Office\Office12\MSACC.OLB\0 and
others with the same path. The file C:\Program Files (x86)\Microsoft
Office\Office12\MSACC.OLB
exists, but it's a file not a folder. The result is always Name Invalis,
Path Not Found and Access Denied.

It seems to me this shows some error,but I am not clear of the exact
implications. Does this meake sense to you?

Thanks

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

 

[David W. Fenton]

=?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?=

It seems to me this shows some error,but I am not clear of the
exact implications. Does this meake sense to you?

I'm in the same boat as you, i.e., it's obviously showing an error,
but I have no idea what it all means! It looks to me like something
to do with 32-bit support and virtualized directories. Other than
that, I can't say. Certainly the fact that it never succeeds in
finding DAO would be a pretty good indication of why it can't work!

 

[Tony Toews [MVP]]

I ran the sysinternals process monitor and got the following when I click
the checkbox selector inside the linked tables manager:

Access tries to "QueryOpen" dao360.dll in several locations:

C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll
C:\Users\Sergio\Documents\dao360.dll
C:\Windows\SysWOW64\dao360.dll
C:\Windows\system\dao360.dll
C:\Windows\dao360.dll
C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll
C:\Windows\SysWOW64\dao360.dll
C:\Windows\dao360.dll
C:\Windows\SysWOW64\wbem\dao360.dll
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\dao360.dll
C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\dao360.dll
C:\Users\Sergio\Documents\dao360.dll

Very interesting. Has anyone suggest registering the dao dll in this
thread yet? For example regsvr32 "C:\Program Files

(x86)\Common Files\microsoft shared\DAO".

An easy way to register a file is to search for both files at one time
(<insert name of your file> REGSVR32.EXE) then drag and drop the
OCX/DLL onto the EXE. As most relevant DLLs and OCXs reside in
c:\<your windows version>\system32 you can try in this directory first
to minimize searching time. If that doesn't find both then go up a
directory level to c:\<your windows version>.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[Jonas Götte]

stupidddddddddddddddddddddddddddddddddddddddddddd

 

[David W. Fenton]

Has anyone suggest registering the dao dll in this
thread yet? For example regsvr32 "C:\Program Files

An easy way to register a file is to search for both files at one
time (<insert name of your file> REGSVR32.EXE) then drag and drop
the OCX/DLL onto the EXE. As most relevant DLLs and OCXs reside
in c:\<your windows version>\system32 you can try in this
directory first to minimize searching time. If that doesn't find
both then go up a directory level to c:\<your windows version>.

Well, on Vista/Win7, you have to run Regsvr32 as admin in order for
it to work (unless you've turned off UAC and are running as admin),
so you might be able to do what you suggest with drag and drop if
you create a shortcut to Regsvr32 and set it to run as admin.

There's also a 64-bit/32-bit issue here, and I dont' know if that's
part of the problem or not.

 

[David W. Fenton]

stupidddddddddddddddddddddddddddddddddddddddddddd

Very helpful.