G
Guest
I have an .adp project that accesses SQL Server. I want a customized version
to prevent users from changing form/macros... So, I modified the Startup
options (Tools/Startup) so that the user was presented with only the features
that I wanted them to use.
However, they can bypass the Startup options if they hold down the Shift key
when they open the .adp file. I read that the Bypass key can be ignored by
setting AllowBypassKey = False. However, there is no code snippet to show you
how to do this when working with a project file (there is an example for an
..mdb file and there is some obscure references to Properties in a
CurrentProject object). I know that a macro named Autoexec should call
(RunCode) a function that sets this property in VBA.
What's the best way (code snippet if you have it) to prevent a user from
bypassing your startup options or securing your interface when using an .adp
project
to prevent users from changing form/macros... So, I modified the Startup
options (Tools/Startup) so that the user was presented with only the features
that I wanted them to use.
However, they can bypass the Startup options if they hold down the Shift key
when they open the .adp file. I read that the Bypass key can be ignored by
setting AllowBypassKey = False. However, there is no code snippet to show you
how to do this when working with a project file (there is an example for an
..mdb file and there is some obscure references to Properties in a
CurrentProject object). I know that a macro named Autoexec should call
(RunCode) a function that sets this property in VBA.
What's the best way (code snippet if you have it) to prevent a user from
bypassing your startup options or securing your interface when using an .adp
project