Forcing to use forms only

  • Thread starter Thread starter Maria Tracey
  • Start date Start date
M

Maria Tracey

I have (almost) secured a database and added users/groups etc.

How do I prevent them from accessing the tables so they have to use the
forms only ?

Of course I need access to the tables etc as the Administrator.

I've read about hiding the database window on startup - I've tried that and
it works initially but if the user closes the form he just has to re-open
the database from the Files menu and the window re-appears.

Thanks for reading.
 
There are a number of things you can do:

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item)
Uncheck the allow special keys (this will disable the F11 key, among
others)

If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes to
forms, reports and modules (If you do this, be certain to keep your original
mdb in case you need to make changes).
 
Joan Wild said:
There are a number of things you can do:

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item)
Uncheck the allow special keys (this will disable the F11 key,
among others)

If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes
to forms, reports and modules (If you do this, be certain to keep your
original mdb in case you need to make changes).
Click to expand...

Thanks for the reply .......

I have a switchboard menu that starts when the database is opened.

I'm quite new at this so I've never created a custom menu before.

I'll give the disable all checkboxes a go too.

Like I said I have tried to hide the database window but if the users just
quits the switchboard form and leaves the database open, you can't see the
database window.
But.........If you then just click on the database entry on the bottom of
the Files menu say for example 1.database.mdb then the database window pops
back up.

PS - Will all this lock me out of the tables too ? If so whats the
workaround ?

Thanks
 
Maria said:
Thanks for the reply .......

I have a switchboard menu that starts when the database is opened.

I'm quite new at this so I've never created a custom menu before.

I'll give the disable all checkboxes a go too.

Like I said I have tried to hide the database window but if the users just
quits the switchboard form and leaves the database open, you can't see the
database window.
But.........If you then just click on the database entry on the bottom of
the Files menu say for example 1.database.mdb then the database window pops
back up.

PS - Will all this lock me out of the tables too ? If so whats the
workaround ?
Click to expand...

Maria - make sure you experiment on a backup. Working on your only copy is like Russian
Roulette.

You can search on Joan Wild in this newsgroup and get lots of good info concerning what
you want to do.

Try holding the <Shift> key while opening a database (.mdb) file. That may circumvent its
startup procedure but a backup will ensure that you can experiment safely.
 
As John says, always test these things out after a backup!

As for the File menu item, if you create your own custom menu, you don't
have to include those items on your menu.

Actually if you uncheck all the boxes on the startup dialog, I believe those
items won't appear; not positive, but test it out.

If you need to bypass the startup options, hold the shiftkey down while you
open the mdb.

Creating a custom menu isn't as onerous as you may think.

View, toolbars, customize...

Click on Toolbars tab, click on New and give a name to your custom menubar.
It'll be saved with the mdb file, so you won't see this when other mdb files
are open. Click on properties and change the type to menubar. The easiest
way to add items to your menubar is to copy them from existing menus. With
the customize dialog still open, go to the File menu, *hold down the ctrl
key* while you drag an item to your menubar. It's important that you use
the Ctrl key while you drag the item, as that will copy (as opposed to move)
the item.
 
Back
Top