T
TimE
I found the problem.
Apparently, the problem was with forms that use queries
that call visual basic functions. I found a setting in
the registry for the MS Jet 4.0 Engine that was different
in the affected machine.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines]
contains a key called 'SandboxMode'. The value of this
key apparently controls access to 'potentially dangerous
VBA code' from Jet expressions or queries. My computer
contained a value of '2' for this, and the problem
computer contained a value of '3'. The '3' value means
the Sandbox mode is used at all times and the '2' value
sets the SandBox mode to be used only for non-Access
applications.
Thank you to those of you who offered suggestions.
TimE
Apparently, the problem was with forms that use queries
that call visual basic functions. I found a setting in
the registry for the MS Jet 4.0 Engine that was different
in the affected machine.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines]
contains a key called 'SandboxMode'. The value of this
key apparently controls access to 'potentially dangerous
VBA code' from Jet expressions or queries. My computer
contained a value of '2' for this, and the problem
computer contained a value of '3'. The '3' value means
the Sandbox mode is used at all times and the '2' value
sets the SandBox mode to be used only for non-Access
applications.
Thank you to those of you who offered suggestions.
TimE