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

Creating a production/run time environment

100+
P: 114
Hello to all, Access Newbie here!

I'm not sure what to call the process in Access, but I have created a couple of forms, a query and report. I want to create a run time enviroment that does not include the Access IDE (tool bars, icons, developer inviorment).

Do not need a menu, just need to start on one of the forms after a user clicks on a desktop icon. Have taken care of the exit with a button using the OnClick [event procedure] with DoCmd.Quit on the form where the exit should take place

What is this process called?
How do I go about creating this user/production enviorment?
Can I go back and make changes/upgrades to a single form after I have done this process?
Are these forms, query, reports kept as seperate files or are they part of the database?

Examples or links of this process would be great!
Thanks
Dec 22 '06 #1
Share this Question
Share on Google+
5 Replies


MMcCarthy
Expert Mod 10K+
P: 14,534
Hello to all, Access Newbie here!

I'm not sure what to call the process in Access, but I have created a couple of forms, a query and report. I want to create a run time enviroment that does not include the Access IDE (tool bars, icons, developer inviorment).

Do not need a menu, just need to start on one of the forms after a user clicks on a desktop icon. Have taken care of the exit with a button using the OnClick [event procedure] with DoCmd.Quit on the form where the exit should take place

What is this process called?
How do I go about creating this user/production enviorment?
Can I go back and make changes/upgrades to a single form after I have done this process?
Are these forms, query, reports kept as seperate files or are they part of the database?

Examples or links of this process would be great!
Thanks

Can you post a reply to this thread on Wednesday/Thursday to bump it up the list. It may not get much attention over Christmas.

Happy Holidays.

Mary
Dec 25 '06 #2

Expert 5K+
P: 8,434
Others can provide much more detail, but to get you started, you can...
  • Automate the startup by creating a macro called AutoExec which opens your form.
  • Protect your source code and make a "runtime version" by converting your database from MDB to MDE. Note, I'm pretty sure this conversion is one-way, so keep a backup copy of your original or you may lose all your work. The MDE doesn't allow access to the source code, and so on.
  • Set up your Windows icon (shortcut) to open the database in runtime mode. I don't think this is foolproof, but it may be enough depending on your circumstances. Wish I could remember how to do it. :) I think you just add "/runtime" onto the command line, but not sure.
There you go, just a few simple ideas for you to play around with. Who knows, by the time you get more details here, you might not need them.
Dec 27 '06 #3

100+
P: 114
Have created a MDE and that looks much better, and created a short cut that works great.

I'm not sure what you mean by the parameter "/runtime". Are you talking about a switch added after the database name in the startup.

Anyway, so far so good. Thanks
Dec 27 '06 #4

Expert 5K+
P: 8,434
Have created a MDE and that looks much better, and created a short cut that works great.
Cool. I hope you remembered to keep a copy of the MDB for development work.

I'm not sure what you mean by the parameter "/runtime". Are you talking about a switch added after the database name in the startup.
Yes. I'm not sure that's the correct way to do it (paging Mary, where are you...), but the Access runtime only allows people to use the database, not do any development work. I think an MDE provides similar results, but have little experience with them.

Anyway, so far so good. Thanks
You're welcome.
Dec 27 '06 #5

MMcCarthy
Expert Mod 10K+
P: 14,534
Cool. I hope you remembered to keep a copy of the MDB for development work.

Yes. I'm not sure that's the correct way to do it (paging Mary, where are you...), but the Access runtime only allows people to use the database, not do any development work. I think an MDE provides similar results, but have little experience with them.

You're welcome.
The mde is the runtime environment as long as access (same version preferably) is installed on the users machine. If not it's a little (a lot :D) more complicated.

Mary
Jan 1 '07 #6

Post your reply

Sign in to post your reply or Sign up for a free account.