Setting up password protection in a different State

  • Thread starter Thread starter Alex Martinez
  • Start date Start date
A

Alex Martinez

Hello,

My company is in California and we have a branch in New York I have access
to the branch server and folder. I am creating a database using Access 2002
in which there will be about 10 users. What I want to do is to start
inmplementing security - User and Group Accounts and WorkGroup Administor
etc. in California, without going to New York. Is this possible? Do I
need to be in New York to put an "mdw" file in the individual PC's? I just
need some advice to what I should look. Any tips will be appreciated.
Thank you.
 
Alex Martinez said:
Hello,

My company is in California and we have a branch in New York I have access
to the branch server and folder. I am creating a database using Access 2002
in which there will be about 10 users. What I want to do is to start
inmplementing security - User and Group Accounts and WorkGroup Administor
etc. in California, without going to New York. Is this possible? Do I
need to be in New York to put an "mdw" file in the individual PC's? I just
need some advice to what I should look. Any tips will be appreciated.
Thank you.
Click to expand...

Alex, I'm doing something similar and based on the great advice from the
folks in this NG, I would highly recommend you look at the Access Security
FAQ
(http://support.microsoft.com/default.aspx?scid=/support/access/conten
t%2Fsecfaq.asp). It will answer your questions and Section 33 discusses
remote administration.

Brian
 
A properly designed & secured multiuser Access database comprises five
things:

1. The "front end" database (mdb or mde file) - this contains all of
the programs (queries, forms, reports & modules) but none of the data.

2. The "back end" database. This contains all of the data but none of
the programs. The front end has links to the actual tables in the back
end.

3. Some means whereby the front end database can re-establish the table
links; for example, if the back end database has been moved to a
different folder.

4. The workgroup (mdw) file which was used to secure the two databases,
and

5. A shortcut which uses the /wrkgrp switch to start the front end
database with the proper workgroup file.

You could develop all of those things locally, then copy them to the
remote site. The usual difficulties (which you must handle somehow)
are:

a. Each user of the database must have their own copy of the front end
database - you should not have many users sharing the same copy, and

b. The shortcut (noted in 5 above) must know the exact folder location
of msaccess.exe, and the front end database file, and the workgroup
file - so you will have to update the shortcuts, somehow, if the
location of any of those three files is different on the target PCs,
compared to your (development) PC.

If most of the above comes as a surprise to you, I would recommend
allocating quite some time to get this all working properly at your own
location. Don't even think about deploying it remotely, until you've
got it working locally!

HTH,
TC
 
Back
Top