Permissions Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an Access Database that has security on it through a workgroup file.
I am the Owner of the database and have admin rights in the workgroup. I
have setup a user and in his permissions I have given him full administrator
rights to the database. When the user goes to create a table or query it
tells him he doesn't have modify permissions to tables. But he actually does
so I am not sure why it is not allowing him to do so.
Anyone know why this would happen even though in User and Group Permissions
it says he has full admin rights?
 
Check to see if he has Read, Write, and Delete permissions to the folder
that the database is stored in.
 
Yes he as all those permissions to the folder that the database is stored in.
This is really confusing me because he should be allowed to modify and add
tables.
 
Playa said:
Yes he as all those permissions to the folder that the database is
stored in. This is really confusing me because he should be allowed
to modify and add tables.
Click to expand...

My guess is that you set up security incorrectly and he is opeing the fiel
with the default MDW and not the one you are using. His default MDW file is
getting him in (which it wouldn't if security were correct), but doesn't let
him modify tables.

Does he get a login prompt when he opens the file or not?
 
Here is the error message i Get if i try and copy and paste an already
existing table or query....."You do not have the necessary permissions to use
the 'MSys Tables' Object. Have your systems administrator or the person who
created this object establish the appropriate permissions for you.

Well I am both the admin and the person who created the database and i have
no clue.
 
Yes he does get a login prompt and it is pointing to the same MDW, I force
them to use the MDW in the shortcut.
 
Let's try one other thing. Create a new user and give that new user the same
permissions. Log on as that user and see if you still encounter the problem.
 
No, I've not actually seen it happen before. "MSysTables" is not one of the
standard system tables, so I'm wondering if there is some corruption in your
database.
 
I actually think that the problem is the Access 2002 database is using an
Access 97 workgroup file. I have read that there was a bug in it, there is a
work around in 97 but haven't been able to find one for 2002.
 
I'm not aware of that bug but, then, there is a lot I'm not aware of.
Perhaps someone else here has experienced that. We have used a 95 workgroup
file for over 4 years with A2K and A2K2 databases without a hitch.

You could try converting the A97 workgroup file to A2K2. If you try this you
will want to do it on a copy of the workgroup file and test it out
thoroughly after the conversion on a copy of your database before you try it
in your production copy. Make good backups!
 
I also have experienced exactly the same problem. If you set this up with a
windows 2000 machine and Access 2000 everything works fine. I've experienced
the problem with windows XP and ACCESS 2002. Fortunately, I did not get rid
of my old 2000 machine and I am still able to do it there.
 
Back
Top