making a copy of a database with restricted user access

  • Thread starter Thread starter Kay
  • Start date Start date
K

Kay

I have developed an Access 2003 database with many tables and forms and other
functions, and I have a number of people who would like to have a copy of the
database for their own use (not the data itself but the forms and tables
etc). So, I would like to save a version of the database that can be
distributed and opened by others but I want to protect the database from
being modified (i.e. lock all forms and tables and permanently hide all
objects, programming and formatting features). Is there a simple way to do
that?
 
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

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 cant 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...

Note that the mde has all of your code stripped out, and users cannot make
changes to forms/repots etc even IF they by-passed the shift key. When you
make a mde, you can NOT REVERSE this process. You MUST keep a copy of the
original mdb. If you going to use a mde, then it is assumed your database is
split. I explain this concept here:

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

So, using a mde means users can't view code or even make changes to forms.
(in fact YOU CAN'T make changes to the mde either...you have to make all
changes in the mdb, and then re-create the mde for distribution to your
users).
 
Excellent suggestion. Thanks! I can see that in that case it is probably
necessary to split the database so that the 'customer' doesn't lose the data
in their tables if they receive an update of the database. Otherwise they
would have to transfer the entire content of all tables into the new version.
Kay
 
Back
Top