User Level Security in a split database?

[scs]

I'm using Access 2003 and I have directions on how to setup User Level
Security in a database. My database is split and the backend is on a
server. If I implement User Level Security in the front end will the
backend be protected at all? Would it be a good idea to use Share Level
Security on the backend? I don't want users to have to enter more than one
password. Advice?

TIA
Steve

 

[Joseph Meehan]

I'm using Access 2003 and I have directions on how to setup User Level
Security in a database. My database is split and the backend is on a
server. If I implement User Level Security in the front end will the
backend be protected at all?

No. Well it will be protected only in that your restrictions placed on
the front end will be functional, but it will not stop anyone from opening
it up directly and doing anything they want.

 

[Albert D.Kallal]

I'm using Access 2003 and I have directions on how to setup User Level
Security in a database. My database is split and the backend is on a
server. If I implement User Level Security in the front end will the
backend be protected at all? Would it be a good idea to use Share Level
Security on the backend? I don't want users to have to enter more than
one password. Advice?

Remember, the idea with security is that a user MUST LOG ON to their
workgroup. Then, during the day, presumably they open and use many different
secured mdb files with that logon. Remember, a user ALWAYS joins a workgroup
first...and THEN opens MDB database of choice.

So, sure, you should consider securing the backend. Securing file abc.mdb
has nothing to do with securing def.mdb. So, if you secure the front end, it
has nothing to do with securing any other file...including the back end. So,
if you are asking do you need to secure each mdb file your plan to us with
workgroup security...the answer is yes. Thus, this would mean that you nee
to secure both front, and back end....

on the other hand, if you are just trying to hide the ms-accss part, and
keep users out of the ms-access inteface, then you don't need any securty at
all. Just create a mde file..and set the correct startup options, and users
will not be able to see, or get into any parts of your code, or forms, or
reprot desings...

 

[scs]

Thanks. I'll setup User Level Security in both.

Remember, the idea with security is that a user MUST LOG ON to their
workgroup. Then, during the day, presumably they open and use many
different secured mdb files with that logon. Remember, a user ALWAYS joins
a workgroup first...and THEN opens MDB database of choice.

So, sure, you should consider securing the backend. Securing file abc.mdb
has nothing to do with securing def.mdb. So, if you secure the front end,
it has nothing to do with securing any other file...including the back
end. So, if you are asking do you need to secure each mdb file your plan
to us with workgroup security...the answer is yes. Thus, this would mean
that you nee to secure both front, and back end....

on the other hand, if you are just trying to hide the ms-accss part, and
keep users out of the ms-access inteface, then you don't need any securty
at all. Just create a mde file..and set the correct startup options, and
users will not be able to see, or get into any parts of your code, or
forms, or reprot desings...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal