Permissions problem

[Guest]

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.

 

[Lynn Trapp]

Arthur,
You need to log on to your database as a member of the Admins group so you
can change the security settings that you implemented.

 

[Guest]

Hi Lynn:

I wasn't sure how to do as you requested. But I did create another
workgroup file and the only change from the original path is it added a "1"
to the original path. Can I go back to the initial workgroup? Basically how
does one log on to a database as a member of a Admins group?

Tx for your kind assistance to date Lynn.

Art

 

[Lynn Trapp]

Yes, you can use the Workgroup administrator to join the original workgroup
file.

 

[Guest]

Lynn:

Sorry Lynn - but the question still remains - how do I find out how to log
on to the admin group? I still cannot open my own file!

Tx

Art

 

[Lynn Trapp]

When you set up security, did you create a new user and add that user to the
Admins group? Are you getting a username/password prompt when you open the
database?

 

[Geoff Taylor]

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.

 

[Guest]

Hi Lynn:

Sorry to keep bothering you - but I have two rather big databases; one of
which I did add another user to the group - not sure if it is admin or not;
and to your second question - no I do not get a username/password prompt. I
am still locked out.

 

[Lynn Trapp]

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]

Arthur,
That suggests that you probably removed the Admin user from the Admins group
without creating a new user AND without setting the Admin user's password.
Let me suggest that you try joining the default system.mdw file that ships
with access.

 

[Guest]

I to am experiencing this ... and urgently need back in.
I was trying to stop the security warnings from coming up and I ran the
sequrity wizard accidentally and had a prompt for a user name and canceled it
(as I had never had to enter before)... now I get the "don't have access.
contact administrator) and it lists me as the administrator and I can't
access...

 

[Lynn Trapp]

Jenn,
Try logging in with a blank password.

 

[Geoff Taylor]

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.

 

[Lynn Trapp]

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.

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


but you

 

[Guest]

Hi Lynn:

Seems that I have opened the proverbial "kettle of worms"! I probably would
now need basic 1 to whatever steps it takes to do as you suggested. How do I
specifically do what you suggest "try joining the default system.mdw file
that ships with access. By the way I have upgraded to Access 2003. Is this
an inherent problem with this version?

Tx for your ongoing help and sorry for the "headaches" I am probably causing.

Arthur

 

[Guest]

Hi Geoff:

Hope that either you, myself or Jenn finally get to the bottom of this
problem. I will watch the ongoing saga with intense interest.

Arthur

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.

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


but you

 

[Geoff Taylor]

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

file

at enable
you

 

[Lynn Trapp]

How do I

specifically do what you suggest "try joining the default system.mdw file
that ships with access.

First, you need to locate that file. Do a search for system.mdw on your
computer. Once you locate it, then you need to open Access without opening
a database. Go to Tools > Security > Workgroup Administrator. Follow the
instructions for joining the workgroup that you searched for.

By the way I have upgraded to Access 2003. Is this
an inherent problem with this version?

No, it's not a problem with the version, but it is evidence that the 2003
wizard does what it is supposed to do better than previous versions have.

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

 

[Lynn Trapp]

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 Arthur
has Arthur
has file file

 

[Guest]

Lynn:

Having followed your instructions - the file now asks me for a Logon name
(defaults to Amin) and a password. Things that I never set! The saga
continues.

Art