Back-End Security question

[Tammy]

Hello -

I have read many threads regarding back-end security and have found
them all useful. I have a couple of (what seem to be basic) questions:

I have a secured front-end and back-end database. (I did use the
security wizard for this.) By using the shortcuts provided, both files
require a password to get in.

Here is the problem: if I try to access the front-end through Windows
Explorer, I do get the prompt stating it cannot be opened. However, I
am able to open the back-end without a prompt.

I'm pretty sure I read a thread that basically stated this is just the
way it is when it comes to the back-end file. Is this true? Can anyone
locate the back-end and have access to the data without being prompted
for their username and password? (Which would allow them access to the
file with full permissions, instead of adhering to the permissions
assigned in the security file.)

I also read that by assigning a password to the back-end file, only the
people with that password would actually be able to open it through
Windows Explorer, which could be a solution. However, I have users who
have permissions to add, delete, update, etc. records, thus, requiring
access to the tables through their linked front-end copy. Wouldn't this
require everyone to have the password to the back-end in order to work
with the data through their front-end file? (In effect, still allowing
everyone access to my back-end through Windows Explorer with full
permissions?)

Thanks for any information you can provide. I hope my questions are
clear.

Tammy

[Rick Brandt]

Re: Back-End Security question

Tammy wrote:

I have a secured front-end and back-end database. (I did use the
security wizard for this.) By using the shortcuts provided, both files
require a password to get in.
>
Here is the problem: if I try to access the front-end through Windows
Explorer, I do get the prompt stating it cannot be opened. However, I
am able to open the back-end without a prompt.

That is not normal nor correct. Your back end is not secured properly if
you can do that.

If you used the database splitter wizard to split the database after
applying security then that is the problem. The splitter wizard creates a
back end that is not secured.

Create a new blank file while logged in as an administrator in your secure
workgroup and then import all of your back end tables into it. This will be
your new secured back end. Apply permissions as appropriate afterwards.
You should find that the new file will be like your front end in that it can
only be opened when using the appropriate workgroup and after logging in.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Tammy]

Re: Back-End Security question

Dear Rick -

Thanks for your comments. I did split the database prior to running
through the security wizard. After splitting, I applied security to
both sides using the same security file settings - this is how the
shortcuts were automatically added to the desktop.

There is only a problem when I try to open the back-end through Windows
Explorer. If I use the shortcut the Wizard provided, I am required to
enter a username and password. But, if a user navigates to the back-end
location through Windows Explorer, the file opens without prompting for
a username and password.

I will give it another try - not sure where I can be missing a step,
but I must be missing it somewhere.

Thank you again!

Tammy


Rick Brandt wrote:

Tammy wrote:

I have a secured front-end and back-end database. (I did use the
security wizard for this.) By using the shortcuts provided, both files
require a password to get in.

Here is the problem: if I try to access the front-end through Windows
Explorer, I do get the prompt stating it cannot be opened. However, I
am able to open the back-end without a prompt.

>
That is not normal nor correct. Your back end is not secured properly if
you can do that.
>
If you used the database splitter wizard to split the database after
applying security then that is the problem. The splitter wizard creates a
back end that is not secured.
>
Create a new blank file while logged in as an administrator in your secure
workgroup and then import all of your back end tables into it. This will be
your new secured back end. Apply permissions as appropriate afterwards.
You should find that the new file will be like your front end in that it can
only be opened when using the appropriate workgroup and after logging in.
>
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com