Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can Access 97 or 200 open MDE file made in Access 2003 1

Status
Not open for further replies.

vpellerito

Technical User
Sep 12, 2006
30
US
Not sure if this is possible but I would like to share an MDE file but others may not Access version greater than 2000.
Can Access 97 or 2000 open MDE files made in Access 2003?

Vince
 
2K users may be able to use the mde depending on the Default File Format selection (Tools|Options|Advanced tab) in the original 2K3 mdb.
However, I do not believe 97 users would be able to open and use the mde.

Let them hate - so long as they fear... Lucius Accius
 
OK. As it turns out. Creating an MDE probably won't solve my real problem. My boss can't run certain functions in the database that makes use of ADOX. He doesn't even have the .dll for ADOX so using a compiled MDE file won't work. What's worse, we can't expect the client to have the .dll either.
Thanks anyway for responding.
Vince
 
...Now, I'm really confused.

My boss does have the .dll file for ADOX in C:\Program Files\Common Files\System\ado\
but for some reason the Reference library in the VBE doesn't show it. So code that tries to repair that link when the database opens won't work.

I tried copying my version of the .dll file to his computer but that didn't work either.

Has anyone experienced this before? Did you come up with a solution?

Vince
 
Unfortunately, I'm not able to help with this - hopefully one of our gurus will jump in [sadeyes]

Let them hate - so long as they fear... Lucius Accius
 
The DLL exists, but has it been registered?

Maybe try in a command window:
Code:
regsvr32 "C:\Program Files\Common Files\System\ado\DllName.dll"


 
Yes, that was the issue, which seems like an odd ball thing... I wouldn't expect that to be the case most often.
Thanks straybullet and JoeAtWork for your responses.
Vince
 
DLL's always need to be registered so that the client knows where to find it.
If the DLL got installed as part of an application, then the installer usually registers it. But if you simply copy the DLL to a directory, the system won't be aware of it.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top