One user unable to access db....

[kbrooks]

This may or may not be an Access problem, I can't figure it out.

I have a small database set up for only 4 or 5 users. I didn't mess with front end/back end because the main function for this db is to alert me of charge corrections I need to make in our system.....before I was getting many voice mails and emails, and this way they're just lumped all together so I can print the whole list off.

Anyway, we have a new employee who needs access to it. I have absolutely no security set up in Access. The db is saved to a folder on our network, and only those employees (and administrators) can access it. In the past, my supervisor set up security but he was gone so I looked at how all the other users were set up and did the same thing with this new user. She can open the db and view the main form, but when she clicks on a button to add/change a record, etc, it gives her an error message of "Action failed".

I had my supervisor go look at how I set up her security but he said it looks fine, so now I'm stumped. If it was a network security problem, I would think she wouldn't even be able to open the db.

Any ideas??

 

[jeremie_ingram]

This sounds like it could still possibly be a networking security issue. I would go to the folder that the Database resides in and RIGHT click it, then select properties. Under the Security Tab select PERMISSIONS. If she is assigned to a group that has READ ONLY persmissions, then she could view it but never update the database.

 

[kbrooks]

She has read/write/modify....same as everyone else that can access it. This is driving me mad! I removed her and added her again as a desperate attempt.....maybe that will work. (I'm not very hopeful!)

 

[jeremie_ingram]

When you added her, did you check mark the two REPLACE boxes at the top? If you are running WINNT or newer, you have file level security. This means that they can access the folder, but if the permissions are not inherited by all sub directories and files withing that folder they will still be unable to access the mdb properly.

 

[J.Windebank]

This is just an idea from someone with little exception, but could the user's version of access perhaps not have the correct references? I think this would bring up a debugging window though and alert you to the problem, but just one thing to check for...