MDE File will not OPEN

[CindyJ]

Converted a database and the application files from 2000 to 2003. The
application converted fine. I am able to make MDE files just fine. When
distributing the MDE files to the workstations, the MDE file will not open.
I am receiving the error.
"The express On Open you entered as the event property setting produced the
following error: Requested type library or wizrd is not a VBA project." What
is wierd is the MDE file will run from my workstation where the conversion
was done from. But the MDE's files will not run from any other workstations.
All workstations are running Microsoft Office 2003. Please help and Thank
you for your time.

 

[Douglas J. Steele]

Sounds as though you might be referencing a library that's not present on
the other machines.

Open the MDB that was used to create the MDE, and go into the VB Editor.
Select Tools | References from the menu bar. Note each of the selected
references (they'll all be at the top of the list). Are you using any other
than the basic ones included by Access? (Allen Browne has a list of what
those basic references are at http://www.allenbrowne.com/ser-38.html) If so,
ensure that they exist on the client workstations as well.

 

[CindyJ]

Doug, I thought of that, but when I copy the entire MDB file to the
workstations,
it works. Just the MDE file gets that error, not the MDB at the
workstations. So I'm thinking that it's not a library registration issue, or
the MDB would not execute? Would it? In addition, how do I check to see if a
library is registered on the client workstation? When I go into the MDE file
on the client workstation. do a CTL-G, Tools the reference is not available.
So how would I check to see which librarys are registered on the client
workstation? Thanks again

CindyJ

 

[Douglas J. Steele]

You need to build the list on a workstation that's running the MDB. Then, on
the workstation(s) that are running the MDE, you need to ensure that the
same version of each referenced library exists in the same location.

I have some code that might help at
http://www.accessmvp.com/DJSteele/AccessReferenceErrors.html

Does the MDE work on any workstation (yours included), or is it failing on
all workstations?

 

[CindyJ]

Doug, The MDE file does work on my workstation.
I will look at the location of the librarys in the MDB file on my station. And
register those on the other client workstations from the same locations. I
know
one of the problems is upgradeing from Access 2000 to Access 2003 on the
client workstations. The install goes to C:\program files\Miscrosoft Office.
WHEREAS
on my station which was a fresh install the programs are in C:\program
files\Microsoft Office 2003". So you are saying that the locations of the
reference library's on the client workstation MUST MATCH the location on my
computer where the MDE file was made from? I know that they do not match due
to the above. So would I have to copy the file from say "Office" on the
client workstation and make a directly called "Office 2003" on the client
stations so I can register from "Office 2003" as on my station?

 

[Douglas J. Steele]

I believe you'll find that none of the referenced libraries are going to be
in the Office folder: they're more likely to be in C:\Program Files\Common
Files\Microsoft Shared or C:\Windows or C:\Windows\System32. Even if they
are in the Office folder, if they're registered components, Access should be
able to resolve them through the registry.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Doug, The MDE file does work on my workstation.
I will look at the location of the librarys in the MDB file on my station.
And
register those on the other client workstations from the same locations. I
know
one of the problems is upgradeing from Access 2000 to Access 2003 on the
client workstations. The install goes to C:\program files\Miscrosoft
Office.
WHEREAS
on my station which was a fresh install the programs are in C:\program
files\Microsoft Office 2003". So you are saying that the locations of the
reference library's on the client workstation MUST MATCH the location on
my
computer where the MDE file was made from? I know that they do not match
due
to the above. So would I have to copy the file from say "Office" on the
client workstation and make a directly called "Office 2003" on the client
stations so I can register from "Office 2003" as on my station?

 

[CindyJ]

Doug, Thank you much for your advise. Could'nt of troubleshooted this
without it.
Problem originated because I did a custom install on my computer where the
MDB/MDE files were made. They were pointing to "Office 2003/Office11".
Where as the client stations installs of Office 2003 were pointing to
"Office/Office11". So I did a re-install of the Microsoft Office Programs on
the client W/Stations pointing to Office 2003/Office11 and ALL WORKED FINE.
Thanks again, your great. PS. I like beer too, I own a bar here in MT.