Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Replication/Save Conflicts

3 views
Skip to first unread message

tig

unread,
Jul 16, 2009, 10:59:00 AM7/16/09
to
Why do we still have Replication/Save conflicts in a single database
(no replicas) when we have the Document Locking functionality turned
on? We are currently on 6.5. It doesn't make any sense.

Any suggestions greatly appreciated.

Christian Zalto

unread,
Jul 18, 2009, 6:33:36 AM7/18/09
to
"tig" <tim....@micorp.com> wrote:
> Why do we still have Replication/Save conflicts in a single database
> (no replicas) when we have the Document Locking functionality turned
> on? We are currently on 6.5. It doesn't make any sense.
>
Are you sure there are no *local* replicas out there?
Check the document properties who has changed the conflicting
documents the last time.
Another possibility could be agents running in the background and
working on the same document someone is just working on.

--
Good luck,
Christian Zalto


Peter Howard

unread,
Jul 26, 2009, 7:33:47 AM7/26/09
to
tig wrote:
> Why do we still have Replication/Save conflicts in a single database
> (no replicas) when we have the Document Locking functionality turned
> on? We are currently on 6.5. It doesn't make any sense.
>
Document locking works only when working with different IDs.
Having two clients or a client and a background agent working with the
same ID, document locking does NOT work.
0 new messages