VBA in Access Runtime MDE not working

[Guest]

I have created an mde version of my mdb file. When I run it with Access
runtime, I get an error when I try to run vba code.

The mde file runs fine in Access, it is just runtime causing the problem. I
changed macro security leve to low, and the problem still exists.

Any ideas would be greatly appreciated.

 

[Douglas J. Steele]

What's the error? And is the error on the machine where the MDB was created,
or on a different machine?

If it's on the same machine, try recreating the MDE.

If it's on a different machine, it could be a problem with the References
collection. Unfortunately, it's difficult to troubleshoot References
problems with MDEs, because you can't get to the References details, as you
can in an MDB. I show one technique that can be used at
http://www.accessmvp.com/DJSteele/AccessReferenceErrors.html

 

[John Vinson]

I have created an mde version of my mdb file. When I run it with Access
runtime, I get an error when I try to run vba code.

The mde file runs fine in Access, it is just runtime causing the problem. I
changed macro security leve to low, and the problem still exists.

Any ideas would be greatly appreciated.

ummm... it would help a lot to know what error you're getting, and
what procedure appears to be causing it.

This may be a bad reference, but at this distance it's more than a bit
hard to diagnose!

John W. Vinson[MVP]

 

[Guest]

Thanks for the reponse. I have a macro that calls vba code via the RunCode
action. While it works fine in the mdb and the mde files using Access 2003,
the runtime version give me an Action Failed message from the macro.

It is as if the macro is not allowed to run the code.

I am creating the installation package in the Developers Extensions Package
Wizard. It is the being installed on another machine that does not have
Access.

 

[Guest]

Thanks for the reponse. I have a macro that calls vba code via the RunCode
action. While it works fine in the mdb and the mde files using Access 2003,
the runtime version give me an Action Failed message from the macro.

It is as if the macro is not allowed to run the code.

I am creating the installation package in the Developers Extensions Package
Wizard. It is the being installed on another machine that does not have
Access.

 

[Douglas J. Steele]

Kinda like pulling teeth with you, isn't it? <g>

What's the VBA code that's failing? (One of the major complaints against
using Macros is that they don't let you trap errors so that you can get
meaningful information to start with when debugging!)

My guess is that it is a References problem, and something in your VBA code
is failing because of it.

 

[John Vinson]

Thanks for the reponse. I have a macro that calls vba code via the RunCode
action. While it works fine in the mdb and the mde files using Access 2003,
the runtime version give me an Action Failed message from the macro.

"Doctor, I don't feel good. What should I take?"

Please post the steps of the macro and the text of the VBA code that
it's trying to execute.

John W. Vinson[MVP]

 

[Guest]

Thanks again for the help. I appreciate the guidance about the references.
The problem ended up being a table linking issue where the message wouldn’t
show in runtime.

One more quick question, is there a way to prevent the message regarding
blocking unsafe expressions when opening an mde file with runtime Access?

I installed the Jet 4.0 Service Pack 8, but I still get the message.

 

[Douglas J. Steele]

Jeff Conrad has information about this at
http://home.bendbroadband.com/conradsystems/accessjunkie/macrosecurity.html