.dll error qustion

[Vgolfmaster]

Hi,

I am trying to open database files for a class at school, and when I open
them I get the following error pop-up message:

"Your Microsoft Office Access database or project contains a missing or
broken reference to the file 'MSAD015.DLL' version 2.1"

If I follow the MS article related to this, and clear the missing reference,
and them reselect it, I am unable to E-mail the finished assignment back to
school (it gets caught in their anti virus filters). If I click past the
error and do NOT fix the missing reference, I am then able to E-mail it
successfully.

Does anyone know what causes this, and if there are other options to correct
this?

 

[Douglas J. Steele]

That makes no sense at all: the anti-virus filters normally just pay
attention to the file extension.

Try changing your file extension from .mdb (or .accdb if you're using that
format) to something else. Also zip the file (Access databases tend to give
a very high compression rate). Give the person at the other end instructions
to unzip the file and rename it back to the original extension.

 

[Vgolfmaster]

Doug, I agree that it doesn't make sense, but it IS happening.

Can anyone explain the root cause of the .dll association error popup? If I
can fix that, I'm guessing the problem will go away. These are database files
that are created by an instructor at school, and when I open them to work on
course work I get the described popup error mssg.

I originally had Office 2003 suite, and recently installed the MSDNAA
version of Access 2007. Then I installed a full suite of Office 2007 ,
enterprise edition. Is it possible something went wrong with the upgrade? Is
it possibly a conflict between the versions (school uses Office 2007
Professional)?

I do not know that the 'dll is even related to the files getting caught in
the schools anti virus block, but just want to correct this error first,
before more troubleshooting.

V

 

[Douglas J. Steele]

The cause of the problem is that you have a different version of the dll, or
else it's in a different location on your machine, then it was on the
instructor's machine. There is no other way to fix it than to delete the
broken reference and add a working one.

 

[Vgolfmaster]

Thanks Doug,

Is there a possibility of copying that .dll file from school, and installing
it to the same directory at home, in order to avoid this from rearing its
ugly head every time I open a database file from school?

Just shooting in the dark here, with crossed fingers!

Vg

 

[Douglas J. Steele]

Unfortunately, no. That particular dll is part of MDAC, and you need the
entire package, not just one dll.

 

[Vgolfmaster]

Thanks again for the reply Doug,

Are you able to shed any light on what would possibly be different on my
computer that would cause this, when no-one else in my class has this issue?
I did not have this issue before I installed the Office 2007 Enterprise
suite, but there were many updates that were installed to; both after the
MSDNAA stand-alone 2007 version of Access, as well as after the 2007
Enterprise suite was installed.

I tried to uninstall them both and revert back to the stand alone MSDNAA
version to try to correct it, but now this error shows all the time and there
is seemingly no getting rid of it. I see numerous instances of people with
the same issue when googling the error, just curious if anyone has been able
to identify exactly what causes it.

I know I won't be satisfied with just fixing the reference every time I open
a new DB project, and am hoping that someone can offer a permanent fix for
this.

Vg

 

[Vgolfmaster]

Doug,

One last follow up if you don't mind. It appears that the particular .dll
file reference might be installed in a different directory on my machine than
what it is on the machine of my instructor at school. It also appears that
copy/pasting the .dll file is not an option, as it is part of the MDAC
installation, and not stand alone.

Are you aware of any possibility of manually installing the same version of
MDAC on my machine, to the same directory being used at school in order to
get a permanent fix for this registry reference? Or possibly a way to
re-register this .dll on my machine to avoid this error popup when opening a
file that was created at school?

Vg

 

[Douglas J. Steele]

It may or may not be possible, depending on what operating system you're
using, what OS the instructor's using and what actual version of ADO.

Sorry that I can't be more explicit.

What's the exact message triggered by your e-mail? Perhaps you can follow up
in a newsgroup related to the e-mail client, to see if they can suggest any
way around that. (Remember, the problem you're trying to avoid really has
nothing to do with Access!)

 

[Vgolfmaster]

Thanks Doug,

Just to clarify, I have my e-mail attachment issue cleared up, so this right
now is only an issue related to Access and the associated .dll error when
opening a file not created locally on this same machine. If this is not the
correct thread for this please point me in the right direction and I will
happily move this to the correct thread. This particular issue seems to be
specific the the installation path and version compatibility of the MDAC
installation. Is there a newsgroup set up specifically for MDAC issues
related to Access?

Vg

 

[Douglas J. Steele]

I'm confused.

So you can now go into the References dialog and correct any problems, and
successfully send the database back to your school? That's the correct way
to fix problems with References: changing the version of MDAC on your
machine could impact other applications, so you're best off living with the
fact that you'll have a one-time fix to do.

 

[Tony Toews [MVP]]

This particular issue seems to be
specific the the installation path and version compatibility of the MDAC
installation. Is there a newsgroup set up specifically for MDAC issues
related to Access?

I'm just curious. What are your references? Could you run the
following code and report back?

Sub ViewReferenceDetails()

Dim ref As Reference

For Each ref In Access.References
Debug.Print ref.Name & " - " & ref.Major & "." & ref.Minor & "
- " & ref.FullPath
Next ref

End Sub


Tony

 

[Vgolfmaster]

Hi again Doug,

Yes, you are correct, I can now undo the missing reference and refresh the
reference and can now send the files back to school with no issues. I guess
it is just a little irritating to have to do this with each new file that I
open from my instructor. Once saved, that particular db file is then able to
be opened without the broken reference error. New db files downloaded from
school then open with the same error, until the same fix is made.

I have also now been told that the instructor is using the Enterprise 2007
version of office, just like I am, so it makes this invalid reference even
more curious. I guess I'm having a hard time accepting that this is the
normal 'fix' for this, and searching in vain for a more permanent fix.

Vg

 

[Vgolfmaster]

Hi Tony,

I am only familiar with Jscript and VBscript, and it won't run in either of
those formats. If you can give me a quick tutorial of how I can run this I'd
be happy to give you those references.

The particular reference error I am getting is related to:

MSADO15.dll

As stated above, it occurs whenever I open a database file created by my
instructor. I can unassociate the reference and then re-associate it once the
db file is open, and then it is OK, but I have to repeat this process for
each and every new db file that I open from school, and there are many.

Vg

 

[Tony Toews [MVP]]

I am only familiar with Jscript and VBscript, and it won't run in either of
those formats. If you can give me a quick tutorial of how I can run this I'd
be happy to give you those references.

Ah, sorry, I was assuming you were familiar with VBA code. But I see
below your error.

The particular reference error I am getting is related to:

MSADO15.dll

As stated above, it occurs whenever I open a database file created by my
instructor. I can unassociate the reference and then re-associate it once the
db file is open, and then it is OK, but I have to repeat this process for
each and every new db file that I open from school, and there are many.

I've successfully avoided ADO so I have no idea as to the proper
method of handling this problem.

Tony

 

[claire thibodeau]

"Vgolfmaster" <[email protected]> a écrit dans le
message de groupe de discussion :
(e-mail address removed)...