If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Intermittent locking problem
Using Access 2003. I have two applications each with their own FE's and BE's
and using .MDE's for user FE's. Each .MDB file is set to "Share", "No Locks" and "record-level" locking. Each app (FE and BE) is located in a separate directory with full directory access for users of the specific app. So not all users of app #1 have full directory access to app #2 and vice versa. App #2 has a comboBox that gets its recordsource using a query based on a linked table to App #1's BE. Usually the comboBox in App #2 is populated and works. But occaisonally when users are in App #1, a message comes up prior to the form (#2)opening indicating that App #1 is in use. Then when the form is opened (#2) the comboBox is not populated. Sometime later the same user can get a populated comboBox. This is an intermittent problem and not user-specific. What could cause the comboBox to sometimes not populate? How to fix? Thanks. |
#2
|
|||
|
|||
Intermittent locking problem
The users need read, write, create, and delete privileges for both BE
database files AND the folders where they are located. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Stu" wrote: Using Access 2003. I have two applications each with their own FE's and BE's and using .MDE's for user FE's. Each .MDB file is set to "Share", "No Locks" and "record-level" locking. Each app (FE and BE) is located in a separate directory with full directory access for users of the specific app. So not all users of app #1 have full directory access to app #2 and vice versa. App #2 has a comboBox that gets its recordsource using a query based on a linked table to App #1's BE. Usually the comboBox in App #2 is populated and works. But occaisonally when users are in App #1, a message comes up prior to the form (#2)opening indicating that App #1 is in use. Then when the form is opened (#2) the comboBox is not populated. Sometime later the same user can get a populated comboBox. This is an intermittent problem and not user-specific. What could cause the comboBox to sometimes not populate? How to fix? Thanks. |
#3
|
|||
|
|||
Intermittent locking problem
Yes, as described in first post. I don't think that explains why this
happens infrequently to the same user or am I missing something??? "Jerry Whittle" wrote: The users need read, write, create, and delete privileges for both BE database files AND the folders where they are located. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Stu" wrote: Using Access 2003. I have two applications each with their own FE's and BE's and using .MDE's for user FE's. Each .MDB file is set to "Share", "No Locks" and "record-level" locking. Each app (FE and BE) is located in a separate directory with full directory access for users of the specific app. So not all users of app #1 have full directory access to app #2 and vice versa. App #2 has a comboBox that gets its recordsource using a query based on a linked table to App #1's BE. Usually the comboBox in App #2 is populated and works. But occaisonally when users are in App #1, a message comes up prior to the form (#2)opening indicating that App #1 is in use. Then when the form is opened (#2) the comboBox is not populated. Sometime later the same user can get a populated comboBox. This is an intermittent problem and not user-specific. What could cause the comboBox to sometimes not populate? How to fix? Thanks. |
Thread Tools | |
Display Modes | |
|
|