Ok I am very new to setting up security so please bear with me.  I have read
several comments here and need some questions answered.  I have developed a
FE BE program, which will be sent to several places.  Because of the security
issues at each individual place they may place the FE BE differently so I
can't come up with just one idea and expect each to play along if you know
what I mean.  My suggest is to place the FE on each user's PC and the BE
inside a folder on a server.  Now for my questions.

1. When I create a MDW is there ever a possiblity when they open this then
open a different program with a different MDW that it could affect the second
one?  The reason I ask some of the places have very sensitive DBs and I don't
want this program to intefere with theirs.

2. I believe what I read was to create a new MDW from scratch and assign the
permissions, then have them place that in the same folder as the BE.  Is this
correct?

3.  Will this prevent others from gaining access to the tables who don't
have permission, including importing them into another DB?

4.  Since I will be making revisons to the DB and will sending out a FE
later on, could this intefere since the user will have different permissions
than the Admin?

5.  Should I make 2 or 3 groups and each group have a separated password?  I
can't add each individual person, since we don't know who they will be.  For
instance the Admin will have complete permissions.  One password for the
daily routine of the user.  Should I provide a third one so when they get new
revisions, it could modify or create tables, etc?


Just curious on how all this will take place before I dive in.    Any
comments on the above would be helpful.

Thanks Fysh, you asked all the questions that I have.  It sounds like we
have very similar situations.

I know this area is something that I do not understand and I am afraid to
get into it.

Is there anywhere that I can go for very plain english type of instructions
that any idiot can follow?

I have the very same situation that Fysh has described so far.  I have read
your replies and I am sure they will help once I get to a point that I
understand them....haha.

TIA,

Lee

Lee, the trick to getting Access user-level security right, is to
follow an explicit list of written instructions - adding and omitting
nothing. The slightest deviation from the instructions, can cause your
database to be insecure. A typical list of instructions is, the Access
Secuerity FAQ - often referenced in this newgroup. No-one has any hope
of getting it right just by running the wizard, or "fooling around"
(not that I'm accusing the OP of that).

HTH,
TC

There's a step-by-step example on my web site that might help but it's no
substitute for the FAQ (there's also a link to them on my web site).

Regards,
Keith.
www.keithwilby.com

In addition to Keith's list, which is good, you can find a list on the
Security page of my website and on Joan Wild's site -- 
http://www.jmwild.com/Accesssecurity.htm

Show quoteHide quote

Thanks, I think that will help.  I do have another question, though.  I am
creating this DB in 2000, but have edited it in 2003 a few times, and I
know that some users will have 97.  If I secure it in 2000, will this cause
a problem with any other version?

TIA again,

Lee

As everyone has said this is no joke.  I played with this for about a week
now.  I beleieve I finally got it down and got my shortcut to work.  I do
have a couple questions though.  I only have 2 users besides the usual in my
db.  One is for all the users the other is for the administrator so they can
get back in.  A login box appears and depending on the name and password what
permissions they will have.  I manually split my db to FE and BE.  I gave the
FE user modify permission on the tables for linking etc. 

Now my questions:
For some reason when I open another DB it still asks for a log-in, why?  I
know someone here will say I missed something, but I can't figure out what. 
Another question is I am going to implement the disable key and make it a
MDE.  Is this all I am going to have to do to complete the security?  Nobody
will be allowed to import my backend is this correct?

Thanks a bunch, this group constantly helps those in need

Show quoteHide quote

Ok I figured out the first question.  I didn't rejoin to the system.mdw.  I
don't recall seeing that in the literature. 

Show quoteHide quote

Fysh wrote:

You seldom need to join *any* workgroup file other-than the standard
one. Securing a database involves creating a *new* workgroup file &
using that with the /wrkgrp switch on the startup shortcut.


That's because the literature would not have told you to join the other
file, in the first place.

HTH,
TC

Because your secure mdw that you used is now the default one to use for all
Access sessions.  Use the workgroup administrator to join the standard
system.mdw that ships with Access.  Use your shortcut for your secure mdb.
All other sessions of Access will use the default system.mdw

You'll have to test this for yourself.  If you've given them permission on
the backend tables, then they'll be able to import.

Joan thanks for the reply, could you answer one more question.  The shortcut
works fine and when I log in I can see the Users and groups.  However, if I
open the db directly then no log in is required and I don't see the Users or
groups.  What could be wrong?

Show quoteHide quote

When you use the shortcut, it is using your secure mdw (and you see the
users and groups that are stored in that mdw).

If you open the db directly, then you are using your default system.mdw,
which doesn't have your users and groups in it.

Two things:
Users and Groups are stored in the mdw file.
If you can even open your mdb using the system.mdw file, then it isn't
secure; you missed a step.

Thanks everyone, it took some time but I got everything working.  I even
incorporated a pop up form that tells them reconnection is in progress and
hourglass set to true during refreshing of links. I converted it to a MDE
along with MDW.  Hopefully this will be enough to keep the snoops out.

Show quoteHide quote

Well done!

TC

Queries being modified
Reuse Secured.MDW file?
Urgent -- Error 3027
Using ADODB.Recordset to a DB with Workgroup Security
Securtiy
Dbase locking others out
Getting the window password
db locked by another user - error 3051
Linking to tables in a secured database from an unsecured database
Split DB, Replicate or UpSize?