Re: Back end database lock-up

Is this a bound form? Or are you programmaticlly executing some updates in an action query or some code?

A bound form should not behave as you describe, but code might lock a whole table.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"zmickle@xxxxxxxxx" <samlambson@xxxxxxxxx> wrote in message
news:884e75d7-adb2-4bcb-a8c0-fc9109f75192@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 13, 3:42 am, "Allen Browne" <AllenBro...@xxxxxxxxxxxxxx> wrote:
Suggestions:

1. Is this on a wired (CAT5) network?
No unstable connections (such as notebooks using WiFi)?

2. You say that users each have a different front end MDB on their own
computers, but then you say they open the front end (singular)
simultaneously. Is each one opening a separate front end MDB file that's on
their own C: drive? (That's best.)

3. Check the open mode and locking strategy of *each* front end.
In A2007, that's Office Button | Access Options | Advanced.
In earlier versions it's Tools | Options | Advanced.
You should see:
- Default Open mode: Shared
- Default Record Locking: No Locks

4. Close all front ends. Make sure the LDB file in the back-end folder is
gone. Then try again. (In practice, it's the first user in who sets the
actual locking mode.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"zmic...@xxxxxxxxx" <samlamb...@xxxxxxxxx> wrote in message

news:d7557be2-e3ee-4707-9795-5abf2307da18@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

> Excuse my noobness. I am managing an access database that is shared
> by 4 users. Management does not want to use any technologies outside
> of access for this application (no SQL Server, etc). I have split the
> database into front end and back end databases and put the front end
> on each of the users' computers. All users can open the front end
> simultaneously, but once somebody updates data in the form, the back
> end locks up.

> What I expect to happen:
> - I assume that access should use optimistic locking (?) that would
> only lock the records that are being updated, but it locks the entire
> database.

> what I've tried:
> - i checked and double checked that the query and form are set to no-
> locks
> - I tried taking out all calculated values (string manipulations) in
> the query
> - I'm not the only one working on this, so there have been quite a few
> other things looked at to no avail.

> I'm stumped. Thanks for any help.

Allen,

Thanks so much for your response

1. Yes every computer has a wired.

2. Each user has their own ACCDB front end on their own C: drive.

3. Each front end is configured as you suggested in Access Options (I
will double check today)

4. The locking file is not created until a user updates the data via
the form. Any computer that has that same form already open can make
changes as well. After an update is made, any new instance of the
form is "not updatable." When the updating users close the form, the
locking file goes away.

Something about updating the query through the form locks the back end
database, then the back end is locked until the form is completely
closed.

I think the problem is occurring at the point that someone updates.

Thanks,

Sam

.