Getting errors opening downloaded .MDE file

[timm88us]

I recently converted an Access DB from 97 to 2003. I created an MDE file and
am attempting to distribute the MDE file using a VB script that copies the
file from a Novell server to the user's hard drive, then opens the copied DB.
I placed the VB script on 4 PC's - 2 worked fine, but on the other 2 I had
to update from Office 2003 SP1 to SP2. No problem. But I get the following
errors after the MDE file opens on those upgraded PC's (using the VB script
to copy the file):

"The expression <expression type> you entered as the event property setting
produced the following error: Requested type library or wizard is not a VBA
project.

*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro."

The error has a link to MS article 283806 but does not help, as this is an
MDE file and References are grayed out. If I copy the .MDB file it works
OK, but I'd rather have the end users use the .MDE file.
Any comments or suggestions are appreciated. Thanks!

 

[Jeff Boyce]

Perhaps the PCs do not have the same set of references for use. If you
place the .mdb on one of those "failing" PCs and then check the code
module/VBA window and the references, do you have any "MISSING"?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[timm88us]

Thanks Jeff, that was a good idea but one I tried already. No references
show missing. I can then create an MDE file and it will work on this pc
(call it PC 1) but not on the others. I just tried updating Office and they
are now at the same build but no luck. I have set the macro security on all
of them to low.
One thing I notice is that when I look at System Info > Access 2003, the
Jet version shows 4.0 on PC 1 , and on others it's not in that list, it's
under JET Core Components and has both Jet 2.x and jet 3.5. I tried to
download jet 4.0 but was told that the pc already had a newer version.
Strange!
Thanks again, and if anyone has any ideas they are greatly appreciated!

Perhaps the PCs do not have the same set of references for use. If you
place the .mdb on one of those "failing" PCs and then check the code
module/VBA window and the references, do you have any "MISSING"?

Regards

Jeff Boyce
Microsoft Office/Access MVP

I recently converted an Access DB from 97 to 2003. I created an MDE file
and
am attempting to distribute the MDE file using a VB script that copies the
file from a Novell server to the user's hard drive, then opens the copied
DB.
I placed the VB script on 4 PC's - 2 worked fine, but on the other 2 I
had
to update from Office 2003 SP1 to SP2. No problem. But I get the
following
errors after the MDE file opens on those upgraded PC's (using the VB
script
to copy the file):

"The expression <expression type> you entered as the event property
setting
produced the following error: Requested type library or wizard is not a
VBA
project.

*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro."

The error has a link to MS article 283806 but does not help, as this is
an
MDE file and References are grayed out. If I copy the .MDB file it
works
OK, but I'd rather have the end users use the .MDE file.
Any comments or suggestions are appreciated. Thanks!

 

[timm88us]

I figured this out. I have Adobe Acrobat 7.0 Standard installed on my pc and
on 2 of the other 4 pc's. I removed Adobe Standard from Access 2003 on my
pc, made another MDE file and voila! it now works everywhere. Note that
I did not actually have to remove Adobe from the pc, just modify it so it
does not meddle with Access. I left it on one of the other pc's but it
makes no difference, it still works.

Thanks Jeff, that was a good idea but one I tried already. No references
show missing. I can then create an MDE file and it will work on this pc
(call it PC 1) but not on the others. I just tried updating Office and they
are now at the same build but no luck. I have set the macro security on all
of them to low.
One thing I notice is that when I look at System Info > Access 2003, the
Jet version shows 4.0 on PC 1 , and on others it's not in that list, it's
under JET Core Components and has both Jet 2.x and jet 3.5. I tried to
download jet 4.0 but was told that the pc already had a newer version.
Strange!
Thanks again, and if anyone has any ideas they are greatly appreciated!

Perhaps the PCs do not have the same set of references for use. If you
place the .mdb on one of those "failing" PCs and then check the code
module/VBA window and the references, do you have any "MISSING"?

Regards

Jeff Boyce
Microsoft Office/Access MVP

I recently converted an Access DB from 97 to 2003. I created an MDE file
and
am attempting to distribute the MDE file using a VB script that copies the
file from a Novell server to the user's hard drive, then opens the copied
DB.
I placed the VB script on 4 PC's - 2 worked fine, but on the other 2 I
had
to update from Office 2003 SP1 to SP2. No problem. But I get the
following
errors after the MDE file opens on those upgraded PC's (using the VB
script
to copy the file):

"The expression <expression type> you entered as the event property
setting
produced the following error: Requested type library or wizard is not a
VBA
project.

*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro."

The error has a link to MS article 283806 but does not help, as this is
an
MDE file and References are grayed out. If I copy the .MDB file it
works
OK, but I'd rather have the end users use the .MDE file.
Any comments or suggestions are appreciated. Thanks!

 

[Jeff Boyce]

Thanks for posting your solution. Someone else will be looking for ideas
some day and find your answer...

Regards

Jeff Boyce
Microsoft Office/Access MVP

I figured this out. I have Adobe Acrobat 7.0 Standard installed on my pc
and
on 2 of the other 4 pc's. I removed Adobe Standard from Access 2003 on my
pc, made another MDE file and voila! it now works everywhere. Note
that
I did not actually have to remove Adobe from the pc, just modify it so it
does not meddle with Access. I left it on one of the other pc's but it
makes no difference, it still works.

Thanks Jeff, that was a good idea but one I tried already. No
references
show missing. I can then create an MDE file and it will work on this pc
(call it PC 1) but not on the others. I just tried updating Office and
they
are now at the same build but no luck. I have set the macro security on
all
of them to low.
One thing I notice is that when I look at System Info > Access 2003, the
Jet version shows 4.0 on PC 1 , and on others it's not in that list,
it's
under JET Core Components and has both Jet 2.x and jet 3.5. I tried to
download jet 4.0 but was told that the pc already had a newer version.
Strange!
Thanks again, and if anyone has any ideas they are greatly appreciated!

Perhaps the PCs do not have the same set of references for use. If you
place the .mdb on one of those "failing" PCs and then check the code
module/VBA window and the references, do you have any "MISSING"?

Regards

Jeff Boyce
Microsoft Office/Access MVP

I recently converted an Access DB from 97 to 2003. I created an MDE
file
and
am attempting to distribute the MDE file using a VB script that
copies the
file from a Novell server to the user's hard drive, then opens the
copied
DB.
I placed the VB script on 4 PC's - 2 worked fine, but on the other
2 I
had
to update from Office 2003 SP1 to SP2. No problem. But I get the
following
errors after the MDE file opens on those upgraded PC's (using the VB
script
to copy the file):

"The expression <expression type> you entered as the event property
setting
produced the following error: Requested type library or wizard is not
a
VBA
project.

*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or
macro."

The error has a link to MS article 283806 but does not help, as this
is
an
MDE file and References are grayed out. If I copy the .MDB file it
works
OK, but I'd rather have the end users use the .MDE file.
Any comments or suggestions are appreciated. Thanks!

 

[Tony Toews [MVP]]

I figured this out. I have Adobe Acrobat 7.0 Standard installed on my pc and
on 2 of the other 4 pc's. I removed Adobe Standard from Access 2003 on my
pc, made another MDE file and voila! it now works everywhere. Note that
I did not actually have to remove Adobe from the pc, just modify it so it
does not meddle with Access. I left it on one of the other pc's but it
makes no difference, it still works.

Oh geez, Adobe Acrobat strikes again with thier cr*p.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/