By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,287 Members | 1,582 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,287 IT Pros & Developers. It's quick & easy.

usys Table Question

P: 110

I (think) I have a problem because I used a usysTable in my database (that is to say, I have a table for system users and I named the table 'usysUsers'). I did this for no reason other than I learned that Access will treat the table as a system table (i.e. hide the table when unchecked). I recognize that this offers nothing.

In any event, I believe that anytime a user accesses the usysUsers table that the entire database is placed in a locked state. (i.e. I get the query messages 'due to lock violations').

This table is only used for the users log and is rarely accessed by admins. However, if this is causing the problem, I can change this with only moderate headaches resulting in the front end.

Before doing so, however, I wanted to ask the question of you - does accessing a system table (specifically a usys table) lock the database.

As always - thank you all so very much for your help and expert opinions - Happy Spring!

Mar 20 '14 #1
Share this Question
Share on Google+
4 Replies

Expert Mod 5K+
P: 5,397
depends on where the table is...
- Split database, frontend, shouldn't be an issue.
- Split database, backend, because the table is potentially locked by the first user, any subsequent users may have issues. This will depend on how the records are being locked.
- AllInOne file, then the table is most likely locked by the first user to open the file and access the table.

Otherwise, I've not had any issue using the usys prefix and I use it quite often to help keep the causual users out of sensitive information.
Mar 20 '14 #2

P: 110
Thanks, ZMBD -

The table is located in the back end. I could understand if only the usysTable was locked but the odd issue I'm experiencing is when a user is accessing the usysTable, I cannot run SQL Commands (Update/Insert/Delete) anywhere in the database without getting the Query Message (due to 'lock violations').

I'm going to try to rename the table and at least eliminate this from the equation.

Thanks again!

Mar 21 '14 #3

Expert Mod 5K+
P: 5,397
Sorry, got tied up.
As I noted, with the USYS in the backend, once locked by the first user, you're stuck.
Is the USYS table linked to any other tables? IF so then I suspect that because the USYS is treated as system, then the other tables are locked at the table level instead of at the record level - I am kindof guessing on that (^_^).

Did renameing the table solve any of the other issues?
Mar 25 '14 #4

P: 110
No worries, zmbd - as always, I'm very appreciative of all you folks do here.

The usysTable is not linked to any other tables. I have updated the table and front end code but not have the occasion to test just yet. I will update this post after I've tested the theory.

Thanks again.

Mar 26 '14 #5

Post your reply

Sign in to post your reply or Sign up for a free account.