Permissions problem

[Lynn Trapp]

Well,
Someone, perhaps inadvertently, has gave the Admin user for that system.mdw
file a password. Now that you are joined to that workgroup file, close
access and delete that system.mdw file. When you reopen access, it should
create a new one for you.

 

[Geoff Taylor]

Lynn...

I have attempted to join every .mwd file that exists in the environment in
which I have been working.
Nothing has changed the behaviour on trying to load my database.

It is an unbelievably stupid security system that entraps the user without
warning.
This has caused me as administrator a great deal of time and my users have
lost half a day's work.

Geoff,
When you run Access there has to be a .mdw file that authenticates users --
even if Admin is the only user. When you run the security wizard it creates
a new .mdw file -- usually called secure.mdw. You may have gotten yourself
into this situation by being joined to that new group and, somehow, having
no valid users who can access the database with that group. Thus, if you
rejoin the original system.mdw file this may fix your problem.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

Lynn
As described in the intial post...
Access 2002 using an access 2000 level database.

As described in the intial post, I have never needed to familiarise myself
with the permissions structure of Access. What exactly do you mean by "join
to the system.mdw file that ships with access"? What do you mean by "you"
are joined?

What version of Access are you using? The first think I would try, Geoff,
is to make sure that you are joined to the system.mdw file that ships with
access.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


Thanks Lynn...

I basically did not "do" anything.
I ran the security wizard to investigate whether this was implicated in
some
unusual record locking.
I have never run it before.
I did not create anything but cancelled out at the first oportunity.
I did not create a workgroup nor users.

There is no login prompt.
All I get is the "You do not have permission to open [name of mdb file]
file.
Get the owner or administrator to change the permissions to enable

you

to
open the file"

As I am the owner and administrator of the database, I find the message
particularly irksome.

This appears to be an 'open manhole cover' with no warning signs or safety
net as several other posters have the same experience.



I opened the security menu to investigate.
Now all users, including me, get the same error message that Arthur
has
described

When you "opened the security menu to investigate" just what did

you
do?

Did
you run the security wizard? Did you create a new workgroup? Did you
create
any new users? Are you getting a logon prompt.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


Arthur...
Access2002
Mdb is Access2000

I have the exact same problem

I have a backend mdb file that has been in use for some time.
I opened the security menu to investigate.
Now all users, including me, get the same error message that Arthur
has
described..

I have never had to deal with 'workgroup' or 'user' permissions

in
the

current Novell environment.
The database has never had passwords nor permissions set.

I am effectively locked out of my own database.
This is despite me having created the mdb and being the admin.

This is an urgent problem. Whilst I have a backup from earlier

in
the

day,
users have updated the backend since then and if I drop back to that
version, data will be lost.



I am the owner/administrator/user of a mdb file. I must have boobed
but
I
wanted to change the security of the macros in that particular file
so
that
it would open always without prompting. Now I cannot open the file
at
all.
I get the error message "You do not have permission to open this
object
file.
Get the owner or administrator to change the permissions to enable
you
to
open the file" - or words to that effect. Hope you can assist.

 

[Guest]

Hi Lynn:

I did what you suggested. Closed access, searched for system.mdw, deleted
it and reopened Access. One of my files opens ok, but the smaller database
now only asks me for a password (no logon name)! Are we getting somewhere
with this yet? It is really infuriating.

Art

 

[Rick Brandt]

----- Original Message -----
From: "Arthur" <[email protected]>
Newsgroups: microsoft.public.access.security
Sent: Thursday, November 25, 2004 5:41 AM
Subject: Re: Permissions problem

Hi Lynn:

I did what you suggested. Closed access, searched for system.mdw, deleted
it and reopened Access. One of my files opens ok, but the smaller database
now only asks me for a password (no logon name)! Are we getting somewhere
with this yet? It is really infuriating.

That is a different issue; the simple file-password feature. Do a Google search
as the file password is very simple to hack and there are several web sites that
describe how.

If you don't remember ever assigning a file password then you could be screwed
as prompting for a password when one was never assigned is also a symptom of
file corruption, usually a type that cannot be repaired.

 

[Guest]

Lynn:

Looks like you have foresaken me. I did receive a note from a Rick Brandt -
no legible signature but a garbled sign-off on hunter dot com! You might
like to look at his message. The problem is NOT different as he says. I do
think this is a problem that microsoft should look at. I would love to hear
your comments. I have never issued a password to any of my access files, nor
do I think the file is corrupted!

Art

 

[Rick Brandt]

Lynn:

Looks like you have foresaken me. I did receive a note from a Rick Brandt -
no legible signature but a garbled sign-off on hunter dot com! You might
like to look at his message. The problem is NOT different as he says. I do
think this is a problem that microsoft should look at. I would love to hear
your comments. I have never issued a password to any of my access files, nor
do I think the file is corrupted!

This part is very simple. There are two kinds of security prompts that Access
can issue. One associated with User-Level Security that asks for a UserName AND
a Password. The other associated with a file level password that ONLY asks for
a password. On the file in question you have indicated the latter.

There are two ways that can cause an Access file to prompt you for a file-level
password. Either someone has applied a password to the file or it is corrupted.
So your file is either corrupted or someone else has put a password on it.

 

[Lynn Trapp]

Geoff,
Without sitting and actually looking at your setup, I don't know what else I
can offer at this point. Access Security is a fine tool, when setup and used
properly.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

Lynn...

I have attempted to join every .mwd file that exists in the environment in
which I have been working.
Nothing has changed the behaviour on trying to load my database.

It is an unbelievably stupid security system that entraps the user without
warning.
This has caused me as administrator a great deal of time and my users have
lost half a day's work.

Geoff,
When you run Access there has to be a .mdw file that authenticates users --
even if Admin is the only user. When you run the security wizard it creates
a new .mdw file -- usually called secure.mdw. You may have gotten yourself
into this situation by being joined to that new group and, somehow, having
no valid users who can access the database with that group. Thus, if you
rejoin the original system.mdw file this may fix your problem.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

Lynn
As described in the intial post...
Access 2002 using an access 2000 level database.

As described in the intial post, I have never needed to familiarise myself
with the permissions structure of Access. What exactly do you mean by "join
to the system.mdw file that ships with access"? What do you mean by "you"
are joined?


What version of Access are you using? The first think I would try, Geoff,
is to make sure that you are joined to the system.mdw file that

ships
with

access.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


Thanks Lynn...

I basically did not "do" anything.
I ran the security wizard to investigate whether this was

implicated
in

some
unusual record locking.
I have never run it before.
I did not create anything but cancelled out at the first oportunity.
I did not create a workgroup nor users.

There is no login prompt.
All I get is the "You do not have permission to open [name of mdb file]
file.
Get the owner or administrator to change the permissions to

enable
you

to
open the file"

As I am the owner and administrator of the database, I find the message
particularly irksome.

This appears to be an 'open manhole cover' with no warning signs or
safety
net as several other posters have the same experience.



I opened the security menu to investigate.
Now all users, including me, get the same error message that Arthur
has
described

When you "opened the security menu to investigate" just what did you
do?
Did
you run the security wizard? Did you create a new workgroup? Did you
create
any new users? Are you getting a logon prompt.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


Arthur...
Access2002
Mdb is Access2000

I have the exact same problem

I have a backend mdb file that has been in use for some time.
I opened the security menu to investigate.
Now all users, including me, get the same error message that Arthur
has
described..

I have never had to deal with 'workgroup' or 'user'

permissions

in to
that

 

[Lynn Trapp]

Arthur,
No, I didn't forsake you. I just left work at my usual time. Take a look at
Rick Brandt's messages about a database password that has apparently been
set or, else, is being prompted for because of some kind of corruption.

 

[Guest]

Lynn:

Rick's messages do not solve any problems - they seem just to add to them!
He sounds very condescending, and perhaps a little aloof. I am seeking help
not criticism. I did not set a password, I am the only one who uses this
database. I am not sure what, if any, chances there are of ever retrieving a
lot of hard work here. It would appear from the other threads, that I am not
the only one who has encountered this problem. You say the security system
for this access version is fine, if set up properly. This is what several of
us want to know. If you can set up security one way - we should be able to
unset it as well. It does not seem to be the case here.

Art

 

[Lynn Trapp]

Rick's messages do not solve any problems - they seem just to add to them!

He sounds very condescending, and perhaps a little aloof. I am seeking help
not criticism.

I never have, and do not now, see anything condescending in Rick's tone. I
think he is a very helpful person. You should take a look once more at what
he has to say, if you are only receiving a password prompt and not a
username/password prompt.

I did not set a password, I am the only one who uses this
database. I am not sure what, if any, chances there are of ever retrieving a
lot of hard work here.

Since you indicated that, with one of your databases, you were prompted for
a password without a logon name then that is an indication of a database
password. Either somebody had to set it or, else, the file has become
corrupted.

Are you now able to open any of your databases without a username/password
prompt?

 

[Guest]

Lynn:

I have re-looked at Rick's notes and tried everything and thought of
everything he has suggested. Nothing is working. As a last resort I have
had to rebuild from an old .bak file. This is really not the way this
situation should be resolved; but I am at a loss how to rectify the original
problem. Now if you can tell me how to change a database file named
"family.bak" to family.mdb I would be very appreciative.

Art

 

[Lynn Trapp]

Right click on the file in windows explorer and change the .bak extension to
..mdb.

 

[Guest]

Hi Lynn:

I run XP Pro and it does not allow the change to any extension as you
suggest. I had to go to DOS and use the rename command. Tx for your aid,
but I still suggest that a more simplified security system should be
installed within this version of Access.

Art

 

[Lynn Trapp]

I run XP Pro and it does not allow the change to any extension as you

suggest. I had to go to DOS and use the rename command.

That's kind of odd. Does it actually not "allow the change" or does it warn
you that it might cause problems? I change extensions on XP all the time.

Tx for your aid,
but I still suggest that a more simplified security system should be
installed within this version of Access.

A more simplified security system would most likely not work at all.
Security is never an easy thing on any system. I'm sure there is some step
that you have missed but can't figure out what it is from your description.

 

[Guest]

Hi Lynn:

I opened Windows Explorer, found my file "sample". I right clicked on the
file name; but all I could change was the name. The "bak" extension was over
to the far right; and out of touch. I did not get both the file name and
extension together to change just the extension. I have my explorer view set
to details? In consequence of your reply about the security system, of
course you are right, it's just the instructions for making any changes are
"scary". I just wanted to have my macros open automatically. All my access
database files are my own - and not to be an egoist - I do trust myself. I
always appreciate your help - especially to the renaming possibility. The
files asking me for a password are now "history" and all have been renamed
and rebuilt to the current status. But if I have the wrong settings set for
windows explorer I would like to know about it. Thanks in advance Lynn.

Art

 

[Joan Wild]

But if
I have the wrong settings set for windows explorer I would like to
know about it. Thanks in advance Lynn.

Tools, Folder Options, View tab. You'll see the option to hide extensions
is checked -- uncheck it.

 

[Lynn Trapp]

to details? In consequence of your reply about the security system, of

course you are right, it's just the instructions for making any changes are
"scary". I just wanted to have my macros open automatically.

There is a reason that we recommend, over and over again, to read the
secuity FAQ several times before you ever start trying to secure a database.
And, then, only do it on a copy of the database, so you can scrap it if
anything goes wrong. Nearly everyone who has been successful in implementing
Access security, including myself, Joan Wild, and Doug Steele, will tell you
that it took us several tries on a test system before we got it right.