bak will not open

[kathy b]

I was applying and preparing to test security on my database on our network
and did create a backup (.bak) database to my personal drive before I copied
to the network. In testing my original database was denied permissions, but
also denied permissions for my backup (.bak) database. Isn't the backup
supposed to be unsecured? I am using Access 2000 . . . is there a work
around?

 

[Tom van Stiphout]

On Wed, 19 Mar 2008 11:53:03 -0700, kathy b <kathy
(e-mail address removed)> wrote:

A backup of an unsecured database is unsecured. A backup of a secured
database is secured.
Workgroup Security is an advanced topic. You just cannot guess at how
it works, or hope that clicking a few menu options will do the trick.
You will have to download, study, and fully understand the Access
Security FAQ from microsoft.com before proceeding. Once you do, you
will recognize the steps that lead you to the situation you are in
now. My guess is you changed the default workgroup file.

-Tom.

 

[kathy b]

Thanks for taking the time to reply . . . I'll ignore the snarky tone.
You are probably correct about the default workgroup file, although I'm not
sure how/when I would have changed it. In the past when I have added
workgroup security my database (.mdb) was secured, but Access created the
..bak file as unsecured. The point being I could always revert back to my
original state if I needed. I guess I'll research this one on my own.

 

[Tom van Stiphout]

On Thu, 20 Mar 2008 09:09:00 -0700, kathy b

No snarkyness was intended. The basic premise however was.
Fortunately ALL unsecured standard system.mdw files are exchangeable,
so you can get one from another computer on which you have not eh...
experimented.

-Tom.

 

[BruceM]

There's no need for the "I guess I'll research this one on my own" stuff.
You did not mention any details of how you applied security, so there was no
way to know if you used a database password or user-level security. If the
latter, are you opening the database by way of a shortcut that joins you to
your new security workgroup file? If not, I expect you either modified the
default System.mdw or used a new mdw as the default workgroup file. Either
way you would probably have some problems opening the database.
What happens when you are denied permissions? Are you prompted for a user
name and password, or do you receive a notice that you do not have
sufficient permissions, or what exactly?