jonathanchye
Registered User.
- Local time
- Today, 16:11
- Joined
- Mar 8, 2011
- Messages
- 448
Hi all,
I am having a very frustrating problem that is now more noticable as my users increases. I am running MS Access 2010 with all my backends split into FE/BE format.
The BE is stored on a network shared drive where all users (should) have full rights. The FE is saved locally on each users desktop. The clients settings are all set to ensure no record locking and the database opens in shared mode. I use queries as recordsource and avoid dlookups where possible. None of my forms have record level locking (all set to No locks)
The problem I have now is that once any client opens any table in the BE the whole BE is locked (laccdb file created). This poses a problem when I run my nightly compact and repair script or when I need to make changes to a table in the BE.
I do not understand why it is locked (no exclusive rights to edit) in this way. I am pretty sure I never had this problem before but maybe back then I do not have so many concurrent users. I also have some hidden forms for maintenance purposes that runs periodical checks with the network BE file... Now some users encounter "this table is locked..." error.
Even opening a form in design mode on the FE seem to create a laccdb file on the BE! It seems to create the lacddb file if any of my forms have a recordsource set as "Dynaset" or "Dynaset - Inconsistent updates"
This thread best describes my problems : http://bytes.com/topic/access/answers/853588-back-end-database-lock-up
I am trying to find out from our IT dept. if our shared drive is a UNIX system (this is the only other possible cause I can see now)
I am just hoping if anyone else here could offer more insight...
I am having a very frustrating problem that is now more noticable as my users increases. I am running MS Access 2010 with all my backends split into FE/BE format.
The BE is stored on a network shared drive where all users (should) have full rights. The FE is saved locally on each users desktop. The clients settings are all set to ensure no record locking and the database opens in shared mode. I use queries as recordsource and avoid dlookups where possible. None of my forms have record level locking (all set to No locks)
The problem I have now is that once any client opens any table in the BE the whole BE is locked (laccdb file created). This poses a problem when I run my nightly compact and repair script or when I need to make changes to a table in the BE.
I do not understand why it is locked (no exclusive rights to edit) in this way. I am pretty sure I never had this problem before but maybe back then I do not have so many concurrent users. I also have some hidden forms for maintenance purposes that runs periodical checks with the network BE file... Now some users encounter "this table is locked..." error.
Even opening a form in design mode on the FE seem to create a laccdb file on the BE! It seems to create the lacddb file if any of my forms have a recordsource set as "Dynaset" or "Dynaset - Inconsistent updates"
This thread best describes my problems : http://bytes.com/topic/access/answers/853588-back-end-database-lock-up
I am trying to find out from our IT dept. if our shared drive is a UNIX system (this is the only other possible cause I can see now)
I am just hoping if anyone else here could offer more insight...
Last edited: