Making limits on what users can view

[krystle h. via AccessMonster.com]

I just finished a large database for my company. It's now time to put it out
their for everyone to use. The problem is if I put it on the system like it
is, everyone will be able to edit and view all files. I need to set user
privileges so that they may only view information and I only want one form to
show (my main switchboard that I created) when people open the database. How
do I do this? And if they only have access to this main form, and not others,
will the information still effectively link back to its tables and queries
and work smoothly?

 

[Albert D.Kallal]

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html


Before you deply, you also need to learn about splitting

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Guest]

In addition to hiding the database window etc. you really should implement
security. Without it even a moderately knowledgeable user can by gain access
to all the objects in the database. You'll find details at:

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

Read this very carefully, and then read it again! If you diligently follow
the instructions in the article its not difficult to set up robust security
for your database.

Ken Sheridan
Stafford, England

 

[krystle h. via AccessMonster.com]

Thanks a lot. That worked out well. The only other thing is that one of the
links from my switchboard open into a database where company profile
information (address, phone#) is shown still has a bar at the top. People
will still be able to delete and edit records in that part. I unchecked all
of the toolbar and menu bar options in "start-up options". Is there anything
else that can be done?

 

[Albert D.Kallal]

. The only other thing is that one of the

links from my switchboard open into a database where company profile
information (address, phone#) is shown still has a bar at the top.

You have to do the same for this database also.

The trick in ensuring that nothing shows, except your menu bar (like my
example) is to un-check ALL of the tool bars, and menu bars, EXCEL the main
ms-access menu bar. If you do that, then when you exit, and re-launch the
database (without the shift key), then they will NOT see any menus, except
yours...

When you need to modify a custom menu bar, you have to display the menu bar
(right click - customize). Modify the menu bar, and then hide it. As
mentioned, the only menu bar you want showing is the main access menu bar.

Of course, during development, you will hold down the shift key so your
startup settings don't run. You then develop for awhile, and then to test in
"user" mode, you exit..and then re-enter the application without the shift
key bypassed. You will likely do this dance all day long as you run/test as
user mode, and then flip back in to developer mode (shift key used..so you
don't get the main custom menu). So, you can't develop, or really modify
things when you run your application with the startup settings...so you must
shift-by-pass them when you want to work.

And, in fact, I use alt-f4 to exit the application...the mdb file should
still be highlighted in the windows explore..so, then you hit enter key
(and, hold down shift key if you need be). This key stroke sequence and
exiting and re-entering the application will occur CONSTANTLY all day long
when you are developing.

When you finally have things just right...you create the mde
you plan to distribute...