write conflict (multi user environment)

[Raymond Geering]

Hello,

I simply can't get around the write conflict problem, even
tough I "googled" quite a lot.

We're running a "Free/Budy" database where several users are chaning
records at a time. In general, users are only editing their appointments
but it might be that somebody is chaning it for somebody else.

So I of course get the typical "write conflict" message when the
record has been edited by two users at a time.

As read in some google groups, I added the timestamp to all
tables.

I also have a "me.dirty = false" in the AfterUpdate Event of
each field..

Well, I found out that I could use response = DATA_ErrContinue
in the Form_Error procudure, but that would simply ignore the
changes. I also tried a "docmd.requery" in the BeforeUpdate
of each field.

But in fact, it's just "trying" what I'm doing but I'm looking for a
real, clean solution.

I simply don't know how I could e.g. lock the records or how I
could trap the message and handle it. It would be ok to me if the
second user would simply overwrite the changes. I could live with
the write conflict message *IF* the "save record" button would work. But
the message will pop up again and again until I choose to cancel my
changes.

Maybe there's also a problem because I have 5 time the same subform
on my form (with different filters)?

It would be very appreciated if somebody could lead me to the
correct way.

/Ray

 

[Baz]

Hello,

I simply can't get around the write conflict problem, even
tough I "googled" quite a lot.

We're running a "Free/Budy" database where several users are chaning
records at a time. In general, users are only editing their appointments
but it might be that somebody is chaning it for somebody else.

So I of course get the typical "write conflict" message when the
record has been edited by two users at a time.

As read in some google groups, I added the timestamp to all
tables.

That will not help with real write conflicts, it only cures the spurious
write conflicts that Access throws up under some circumstances.

I also have a "me.dirty = false" in the AfterUpdate Event of
each field..

That's insane.

Well, I found out that I could use response = DATA_ErrContinue
in the Form_Error procudure, but that would simply ignore the
changes. I also tried a "docmd.requery" in the BeforeUpdate
of each field.

That also is insane.

But in fact, it's just "trying" what I'm doing but I'm looking for a
real, clean solution.

I simply don't know how I could e.g. lock the records or how I
could trap the message and handle it. It would be ok to me if the
second user would simply overwrite the changes. I could live with
the write conflict message *IF* the "save record" button would work. But
the message will pop up again and again until I choose to cancel my
changes.

If this were a genuine write conflict between two users, then the "Save
Record" button would work. The fact that it doesn't suggests that your form
design/logic is causing the write conflicts, they are not being caused by
concurrent updates by different users.

Maybe there's also a problem because I have 5 time the same subform
on my form (with different filters)?

I think you are very close to the truth here. That sounds like a moderately
crazy design, what exactly are you trying to achieve? Also, do you have a
trigger which does updates?

It would be very appreciated if somebody could lead me to the
correct way.

I think you will need to give some more information about your design.

 

[Alan Z. Scharf]

Maybe there's also a problem because I have 5 time the same subform

on my form (with different filters)?

Why don't you have 1 subform, with the filter selectable from a listbox,
dropdown, or radio buttons.

Alan