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

Question about mde

P: n/a
Hello,

I am working on a project that I need to ship out as an MDE file. It
is a one form 2 table database that I want the user to only see the
one form. I have hidden the tables from view and want to hide all the
menus and toolbars also. Will also close the shift key bypass so they
do not see the database window.

My question is:

I hide all menus and toolbars in code rather than the options menu of
the database? This will be on a drive with other databases that the
people need to use--I have noticed that when I set preferences in the
options menu--they do not hold on a different machine, and also that
the preferences are the same for all dbases on the mchine where my
program resides. I currently hide everyting by attaching the code to
the open event on the form--and then reverse it on the close event so
if they have to go to a differnt database they have their menus, etc.
Is this correct design?

Thanks
Bob
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
al*****@cox.net wrote:
Hello,

I am working on a project that I need to ship out as an MDE file. It
is a one form 2 table database that I want the user to only see the
one form. I have hidden the tables from view and want to hide all the
menus and toolbars also. Will also close the shift key bypass so they
do not see the database window.

My question is:

I hide all menus and toolbars in code rather than the options menu of
the database? This will be on a drive with other databases that the
people need to use--I have noticed that when I set preferences in the
options menu--they do not hold on a different machine, and also that
the preferences are the same for all dbases on the mchine where my
program resides. I currently hide everyting by attaching the code to
the open event on the form--and then reverse it on the close event so
if they have to go to a differnt database they have their menus, etc.
Is this correct design?


Some options are file specific and some are Access installation specific. You
should be using the startup options to hide the menus and toolbars as that is a
file specific setting. You also should not be programmatically setting any
Access level options unless you change them back when your app is terminated.
Most of the behavior those options affect can be controlled by other means than
messing with the user's settings anyway.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.