By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,478 Members | 1,604 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,478 IT Pros & Developers. It's quick & easy.

Running in Runtime

P: n/a
Hi,
I am distributing an access database to systems that all have office
installed on them. Is there any way to force this database to run in
runtime mode - other than the /runtime switch? Are there any security
advantages to doing this?
Thanks

P.S. How do I keep my email address from showing up for all the
junkmailers?

Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Pachydermitis wrote:
Hi,
I am distributing an access database to systems that all have office
installed on them. Is there any way to force this database to run in
runtime mode - other than the /runtime switch? Are there any security
advantages to doing this?
Thanks

P.S. How do I keep my email address from showing up for all the
junkmailers?


You can use the following to check if it is running in the runtime and exit the
app with a message if it's not.

syscmd(acSysCmdRuntime)

That will return True when in runtime mode.

The runtime automatically prohibits access to the db window and disables all
built in command bars, but I don't think achieving that with the /Runtime switch
is an more secure than simply unchecking those options in Startup and disabling
Access Special Keys and the bypass key since the above suggestion to "force"
Runtime mode relies on the user not holding shift to start the app anyway.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Nov 13 '05 #2

P: n/a
> runtime mode - other than the /runtime switch? Are there any security
advantages to doing this?


Well, when you use the runtime switch, you do NOT see the ms-access menu bar
while you application loads, and THEN your custom menu bars etc show. So,
use of the runtime switch prevents users from every seeing the ms-access
tool/menu bars appear for a short time while your application loads. In
addition, with the runtime switch, users will NEVER see the ms-access ICON
appear in the application, (and again, then your icon appears AFTER the
startup stuff has completed). Further, use of the runtime switch also
disables the shift key by-pass.

So, there is a number of behaviors that are more desirable when you use the
runtime switch..
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 14 '05 #3

P: n/a
On a related note if you're interested you could distribute an .mde
file which is the same as the .mdb file except that design mode is
removed from everything but tables, queries, and macros.

(Tools | Database Utilities | Make MDE File)

Best regards,
J. Paul Schmidt, Freelance Web and Database Developer
http://www.Bullschmidt.com
Access Database Sample, Web Database Sample, ASP Design Tips
I am distributing an access database to systems that all have office
installed on them.


Nov 14 '05 #4

P: n/a
Thank you all for the runtime tips. It sounds like it doesn't do
anything that I can't already do in other ways.

Nov 15 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.