Splitting Database and Security Issues

[Emine]

Hi Everyone!

I got several issues here and I really need a Step-By-Step Instructions on
the following please!! BTW the database will be placed on a network and used
by several people.

1. I've split my database. Now I have a backend Db with only tables on it.
Where are the other objects (i.e, forms, queries, reports)? Is the backend
Db only used by the Admin? If so, why do I not have access to the other
objects? Did I do something wrong.

2. How do I make my Db an executable file or do I need to make it
executable? And what purpose does it serve? I don't want someone who knows
about the shift key or the F11 key to open the database and play around with
it.

3. How do I setup security? Where do I set it up frontend and backend.
Can I setup log on passwords when setting up security?

4. How do I hide the menu bar on top so that the users do not play around
with the Db and are allowed very limited features (i.e, print, view and maybe
couple of others).

My Db is completed and I really need help to finalize it so that it can go
live for testing by other users. PLEASE PLEASE can someone help me.

 

[BruceM]

The back end is the data. It contains only tables and relationships. It is
an mdb file, and does not need to be changed into an executable.

As for the location of the front end, only you know that. How did you go
about splitting? If you used the wizard or created a copy, the FE is around
somewhere. To split a database manually you would delete the tables from
the FE, and delete everything but the tables from the BE. Then in the front
end click File >> Get External Data >> Link tables, and link to the BE
tables.

Click Tools > Startup to disable use of th F11 key, to disallow built-in
menus, etc. Be sure to create your own development copy, as it can be
difficult to get back in if you disallow the shift bypass, etc.

This link contains several links to security information pre-Access 2007.
For Access 2007 format I do not know the procedure. I found Jack
MacDonald's paper to be very helpful, but you should check out several at
least of the other links, including particularly the Microsoft FAQ.

 

[BruceM]

Forgot the link:
http://www.geocities.com/jacksonmacd/

The back end is the data. It contains only tables and relationships. It
is an mdb file, and does not need to be changed into an executable.

As for the location of the front end, only you know that. How did you go
about splitting? If you used the wizard or created a copy, the FE is
around somewhere. To split a database manually you would delete the
tables from the FE, and delete everything but the tables from the BE.
Then in the front end click File >> Get External Data >> Link tables, and
link to the BE tables.

Click Tools > Startup to disable use of th F11 key, to disallow built-in
menus, etc. Be sure to create your own development copy, as it can be
difficult to get back in if you disallow the shift bypass, etc.

This link contains several links to security information pre-Access 2007.
For Access 2007 format I do not know the procedure. I found Jack
MacDonald's paper to be very helpful, but you should check out several at
least of the other links, including particularly the Microsoft FAQ.

 

[John W. Vinson]

Just to add to Bruce's comments...

Hi Everyone!

I got several issues here and I really need a Step-By-Step Instructions on
the following please!! BTW the database will be placed on a network and used
by several people.

1. I've split my database. Now I have a backend Db with only tables on it.
Where are the other objects (i.e, forms, queries, reports)? Is the backend
Db only used by the Admin? If so, why do I not have access to the other
objects? Did I do something wrong.

If you used the splitter wizard on MyData.mdb you should now have two files:
MyData.mdb, the new frontend containing the forms, reports, etc. and links to
the tables; and MyData_BE.mdb, with the tables.

The user sill use a copy of MyData.mdb or (better) MyData.mde - see below.
That copy will use the tables in the backend, via the links. There is no
"Admin" involved.

2. How do I make my Db an executable file or do I need to make it
executable? And what purpose does it serve? I don't want someone who knows
about the shift key or the F11 key to open the database and play around with
it.

You cannot make a database into an executable, period. One thing you can do is
Tools... Database Utilities... Make MDE to save a copy of the database as a
MDE file; this disables the ability to change the design of forms and reports,
and removes all the VBA source code. You must keep a copy of the MDB file
around so you can make design changes; when you do so, just make and
distribute a new MDE.

You can use the Startup menu option to turn off most of the ways that a user
could mess things up. You may want to create some custom toolbars containing
the features you want the user to have, and turn off the builtin toolbars.

3. How do I setup security? Where do I set it up frontend and backend.
Can I setup log on passwords when setting up security?

Download the Microsoft Access 2000 Security FAQ:

http://support.microsoft.com/kb/207793/en-us

Read it. Read it CAREFULLY, cover to cover. Get a good night's sleep; read it
again, even more carefully. Follow the instructions scrupulously.

If you're using 2007 you should be aware that you cannot use security in an
ACCDB/ACCDE database, it's been removed.

4. How do I hide the menu bar on top so that the users do not play around
with the Db and are allowed very limited features (i.e, print, view and maybe
couple of others).

The Startup menu lets you turn off the toolbars.

My Db is completed and I really need help to finalize it so that it can go
live for testing by other users. PLEASE PLEASE can someone help me.

See Tony Toews' website
http://www.granite.ab.ca/access
He has a good section on deployment.