protect master copy of front end database

[dnr]

Hello!

I have a front-end/back-end database I manage for our department. There are
approximately 80 users of this database with the users having a local copy of
the front end installed on there PC.

When designing this database I based my design on the one by Danny
Lesandrini at
http://www.databasejournal.com/feat.../Automatically-Deploy-a-New-Access-Client.htm

So basically, I have a master copy of the front end database on the server
and the user's local copy upon opening runs a program that checks if they
have the most current version on their system, if not it tells the user they
need to update to the most current version. When the user hits ok, it runs
an update which basically creates a backup of their current version on the
local computer erases the current database and copies the master copy to
their person computer. This works well, except for a few problems, which is
where I need the help.

Some users have found the master copy of the front end and have been using
it, can I protect the master copy so only administrators can use it, but then
remove the password protection as it downloads to their local computers?

There are three administrators for this database...
The other problem is, this database is fairly new and we are always working
on tweaking the database. If we are updating the master database it creates
a .ldb file. If a user opens their database, and it needs to update to the
most recent version and the .ldb file is currently in the master database
folder the update causes an error, and I have to go and copy the database in
proper location of the local computer. I am wondering if there is code I can
write that if an update is required, it would check for the .ldb file. If
the .ldb file exists it would bypass asking the user to update the database.

Any suggestions would be very appreciated.

Thanks - dnr

 

[Douglas J. Steele]

Your admins shouldn't be working on the master copy.

Like your other users, they too should have their own copy of the front-end,
and make all their changes there. Once they know the changes are okay,
they'd then replace the master copy.

 

[dnr]

Thanks for the response Doug - good suggestion - I will work on that. Any
suggestions on how to protect the master copy - so people can't go in it, but
it still can be used as the copy to update all the local copies. Thanks - dnr

 

[Dale Fye]

dnr,

The way I do this is in the Startup form of the application, I test to see
whether the currentproject.Path is the folder on the network. If it is, I
advise the user:

"You cannot run the application from this location. Copy the application to
your personal computer and try again!".

and then I use Docmd.Quit to close the application.

--
HTH
Dale

email address is invalid
Please reply to newsgroup only.

 

[Keith Wilby]

Thanks for the response Doug - good suggestion - I will work on that. Any
suggestions on how to protect the master copy - so people can't go in it,
but
it still can be used as the copy to update all the local copies. Thanks -
dnr

Apply user-level security. Disable all start-up options and provide custom
menus. Disable the bypass key. Provide an mde front end. Not a trivial
task.

Keith.
www.keithwilby.co.uk