I have an ADP that runs fine in Access XP but in Access 2003 this statement:
    currentproject.accessconnection
produces this error:
    error in loading DLL

Does anyone know which DLL contains the code for this statement? Better yet, when Access produces really unhelpful error messages like this is there any way to find out exactly what the problem is?

I have tried running the Office repair process. I want to avoid reinstalling Office 2003 if possible (because I will lose all my customizations) but if it is the only way then so be it.

PS I am really annoyed that the error message does not say which DLL it cannot load - this seems incredibly lazy coding.

R

__________________
R

Try looking the visual editor tools, reference and check for missing library or dlls

Jaime E. Maccou

All the references that should be there, are there. I know this for sure because THE VERY SAME ADP file runs under Access XP but not under Access 2003.

To be clear:
The ADP file and the SQL database reside on machine A
Access 2003 is on machine A
Access XP is on machine B

When Access 2003 runs the ADP it gets the "error in loading DLL" message, but Access XP runs the very same ADP (not an identical copy, the very same file) okay.

So clearly on machine A there is either a missing or faulty DLL. I just need to know WHICH DLL is missing/faulty?

FYI
These are the references that are ticked:
VB** VBA
MSACC.OLB Microsoft Access 10.0 Object Library
STDOLE2.TLB OLE Automation
MSADO26.TLB Microsoft ActiveX Data Objects 2.6 Library
SQLDMC** Microsoft SQLDMO Object Library
MSCOMCT2.OCX Microsoft Windows Common Controls-2 6.0 (SP4)

(** these locations are so long that not all the filename can be seen)

R

Is there no way of working out which DLL the message "error in loading DLL" is referring to?

Is there no way of working out which DLL the statement "currentproject.accessconnection" resides in?


R

Hi Richard,

Did you ever figure out how this problem occurred, or even how to fix it? I'm currently having the same problem with a database I have exported.

Cheers

Jon

Jon Satchwell

Richard,
I had a similiar problem except with an .mdb. The file, which resides on a share file on a server, ran fine on my co-workers machine. But I got "error 48- missing dll" on a GetObject function call in an button click event from my machine.

The bottom line was the file ran fine AFTER re-installing Access (2K) AND the OS.

HTH,
Loralee

I have a similar problem in that I get the 'error in loading dll' message when going to entering the vb editor. Consequently none of the code runs correctly.

The references from the 'Tools' menu say that MSo9.dll is missing (which it isn't) but doesn't allow it to be unchecked and closed then restoring it as suggested by MSDN Knowledge base as a method of refreshing the references. The dll is exactly where is should be in the path shown on the references screen.

Now the puzzling thing is that it is a copy database that has had data entered into it only from Access 2003 users (developed on Access 2000 pc). They have not modified the database in any other way.

The original copy database loads fine!

There is nothing peculiar about the database, only default dlls apart from the DAO library.

The only solution I can think of is to copy the tables over to the original database. I would rather have an explanation.

That only means that you have the correct references for Access 2002 (XP) with the same version of ADO/MDAC. That does not mean the reference will be correct for a machine with Access 2003.

My first thought is that the ADO/MDAC libraries are not the same version.

__________________
Boyd Trimmell aka HiTechCoach (.com)
Microsoft Access MVP Alumni 2010-2015

This problem occured in many different files after an overdue migration from 2000 to 2003, for 3 different MDB files originally created in Access 2000. I experienced something similar when opening in Access 2007 and 2010 but the fix was literally just re-enabling the references via Tools menu in the VB Editor.

If you upgraded from Office 2000 to 2003, this was the mskb that resolved the issue for me at least. Might be worth trying. http://support.microsoft.com/kb/899861

Regards,
Jason Shinkle
jason@tecktronic.net