Developer Forum

Hi Newsgroup,

I have got an environment (Access '97), where several frontends are
connected to one backend which is to be replicated with another backend.

When in a frontend a record is edited and at the same time a synchronization
of the connected backend takes part, then there may come the message:' This
record has been changed by another user since you started editing it. If you
save the record, you will overwrite the changes the other user made. ...'

As far as I see, the only changes by 'the other user' may be in the
replication fields updated by the synchronization process.

Does anyone know if it is possible to avoid this message or how to handle it
(without user inteaction)?

Sincerely,
Andreas

You can set up pessimistic locking, which will keep the second process from
even getting in to try to update.


--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.




synchronization
This
you
it

I thought about opening the database with pessimistic locking too, but I am
afraid of two possible problems:

1. When the first user is editing a record a second user may not be able to
edit a different record which is located in the same locked page as the
first record.

2. What happens if the synchronizing process finds a locked record? Does it
stop or does it produces messages which have to be handled? And how are
records handled by the synchronization process which are not edited but
locked because they are located on the same page as an edited record?

Sincerely,
Andreas

"Michael (michka) Kaplan [MS]" < XXXX@XXXXX.COM > schrieb im

from


...'
handle

"Andreas Grahn" < XXXX@XXXXX.COM > wrote...

am
to

If you realistically considered (a) the odds of this happening, and (b) the
user experience of that warning versus the one you hit now, you will likely
not see this as being much of a problem?

it

In the worst case, it is a data error, but one that is unlikely to happen
and one that if it does will clear the next time you sync. Intelligent
scheduling of synchronizations can work around that....


--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.





backend.
If