Re: Record currently locked - 3218

Have you split this database, so that each user has their own separate copy
of the front end (program mde), all connected to the same back end data mdb?
If that is a new concept, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html

If it is split, and set up with optimisitic locking, people should be seeing
the conflict dialog rather than error 3218.

--
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.

"Janis in Minnesota" <JanisinMinnesota@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:6400301B-7775-446F-B919-D7B708F54C1A@xxxxxxxxxxxxxxxx
Wow. The MDE's already have no default record locking, and in the sub
form
as well as main form, no locking. It almost seems like if a user is
entering
containers, and another user opens the main Entry form and starts entering
containers, we get the conflict.

If you know of anymore information that would be awesome. This worries
me
as this is such a simple form and makes me wonder about the complex forms
that are in use.

Thanks soooooo very much!!!!!!

Janis

"Allen Browne" wrote:

Janis, this could be a genuine locking conflict.

What kind of locking are you using? The default is optimistic locking,
and
it is the best approach for the vast majority of JET databases. Verify
that
you have No Locks chosen in:
Tools | Options | Advanced | Default record locking.
and also in the Record Locks property of your form and subform.

With optimistic locking, the record is locked only during the write
operation, which is a fraction of a second. If another user/process has
written a change since the user began editing, they are then presented
the
Write Conflict Dialog, where they should discard their changes, and have
another go. Provided your users are trained to do this, this strategy
were
extremely well.

If you already have optimistic locking and you are still seeing error
3218,
and there is no other extended process that could be holding a lock,
something else is wrong. If this is Access 2000 and later, you might
consider unchecking the box for:
Tools | Options | Advanced | Open databases using Record Level
Locking
Ideally, this check box should reduce the occurrance of locking problems,
but there are some scenarios where it actually makes it worse. I have
only
experienced this when executing a whole series of updates and deletes
inside
a transaction, but it might be worth experimenting with.

"Janis in Minnesota" <JanisinMinnesota@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message
news:9DA69683-CD04-4534-88E8-6C92BB5110B5@xxxxxxxxxxxxxxxx
I have a main form (Entry), and a sub form - continuous -
(EntryContainer).
The sub form is a simple table holding 2 pieces of information
(container
information) and the EntryID that links on the main form. When
multiple
people are entering container information via an MDE into the Entry
form,
SOMETIMES the error The error:
'Could not update; currently locked' - 3218 error

There is absolutely no programming or code behind this simple sub form.

The relationships are correct - EntryID in table Entry to conEntryID
in
table ContainerEntry - 1 to many, cascading updates and deletes.

Any help? I have exhausted all discussion threads to no avail.


.

Relevant Pages

  • Re: Record currently locked - 3218
    ... Yes each user is running off of an MDE, the tables are on the server MDB. ... containers, we get the conflict. ... With optimistic locking, the record is locked only during the write ...
    (microsoft.public.access.modulesdaovba)
  • Re: Informix beats Oracle
    ... program outside the database, whereas it's my impression that Oracle folks ... Oracle simply because it's a lot different than most. ... To me optimistic locking is an entirely different beast and Informix had support for it for years and DB2 Viper 2 is introducing it. ... You look for a seat going from A->B and you get a set of possibilities back. ...
    (comp.databases.informix)
  • RE: Error Message
    ... I do need help with Optimistic Locking -- thanks again. ... > Your database is corrupt. ... More than one user opening and using an Access database file ... which we use to log in and track incoming jobs. ...
    (microsoft.public.access.formscoding)
  • Re: strategy for record locking in multiuser environment
    ... >overwrite another users entries and so each user can see the changes or ... Access default is optimistic locking and it does't do pessimistic locking well ... that changes have been applied to the database ...
    (borland.public.delphi.database.ado)
  • Re: "realistic" buffering?
    ... You would have to use a combination of optimistic locking and manual code to ... I want to allow another process to update fields that the current view ... With any database you would have to come up with some way of handling this outside of the database itself. ...
    (microsoft.public.fox.programmer.exchange)
Loading