Error in Loading DLL

  • Thread starter Thread starter John Reichard
  • Start date Start date
For anyone who is following this thread, I was able to convert John's database into a .mde file
without too much problem. The first issue was that the .mdb file was received with a read only
attribute set. There were no code modules, so a new one needed to be created in order to look at
Tools > References... However, the read only attribute was preventing one from creating the new
module. After removing one reference marked as MISSING (on my PC), and removing several other
non-essential libraries that were checked, I clicked on Debug > Compile. Then I deleted the new
module I had just created. The database then converted to a .mde file without any problems.

Tom

__________________________________________

Beyond that, is it possible to arrange for someone to
actually look at the database and try to convert it
themselves?
Click to expand...

Sure, I'll take a crack at it if you send me a copy. I'll provide a *real* e-mail address in a
private message to you.

Tom
_____________________________________


Tom:

No problem. So I guess I'm back to the problem of
getting the .mde file to convert. I do have Access 2000,
so once I figure out what is wrong, I can create an
Access 2000 .mde file. If anyone has any more
suggestions to solve my problem I'd love to hear it.
Beyond that, is it possible to arrange for someone to
actually look at the database and try to convert it
themselves? It's probably not the norm, but I really
need to get this solved. Thanks.

John
-----Original Message-----
John,

Sorry, I guess I gave you some incorrect information
Click to expand...
last week when I stated that you could open
an Access 97 .mde file in later versions of Access. I
Click to expand...
thought I had remembered that it would
work okay. Turns out that you can open an Access
Click to expand...
2000 .mde file in Access 2002 without any such
error message. I suspect that you can open an Access
Click to expand...
2000 .mde file in Access 2003 as well,
although I cannot test this because I haven't bought
Click to expand...
Office 2003. So, it looks like you'll have
to have two flavors of your front-end database: An
Click to expand...
Access 97 .mde for your Access 97 users, and
an Access 2000 .mde for your Access 2000, 2002 and 2003
Click to expand...
users. I don't think you'll need to
 
You da man, Tom!

;-)

--

Brian Kastel


--Original Message----------------

For anyone who is following this thread, I was able to convert John's
database into a .mde file
without too much problem. The first issue was that the .mdb file was
received with a read only
attribute set. There were no code modules, so a new one needed to be
created in order to look at
Tools > References... However, the read only attribute was preventing one
from creating the new
module. After removing one reference marked as MISSING (on my PC), and
removing several other
non-essential libraries that were checked, I clicked on Debug > Compile.
Then I deleted the new
module I had just created. The database then converted to a .mde file
without any problems.

Tom
 
Just to be argumentative, you don't need to create a module to check the
references. Simply being in the VBE allows you to check the references, so
simply using Ctrl-G to go to the Immediate Window is sufficient.
 
Hi Doug,
Just to be argumentative, you don't need to create a module to check the references.
Click to expand...

This seems to be true for Access 2000 and 2002 (and likely 2003 as well). I'm having a harder
time convincing myself that your statement is true for Access 97 databases. How exactly do you
check references in Access 97 without creating a new module? Recall from John's initial message
that he indicated that he was using Access 97.

Tom
_________________________________


Just to be argumentative, you don't need to create a module to check the
references. Simply being in the VBE allows you to check the references, so
simply using Ctrl-G to go to the Immediate Window is sufficient.
 
Open the Debug Window, using Ctrl-G, provided you haven't selected the "keep
debug window on top" option. (If you have set that option, then yes, I
believe you need to create a module)
 
Thanks Doug.

I did have the option "keep debug window on top" selected in Access 97. I was able to check the
references without creating a new module after deselecting this option.

Tom
______________________________________


Open the Debug Window, using Ctrl-G, provided you haven't selected the "keep
debug window on top" option. (If you have set that option, then yes, I
believe you need to create a module)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

______________________________________
 
Back
Top