Very very funny, familiared and important issue. Mostly everyone has faced this issue. The issue is that I am having the employee database on main server. And I have a lot of replica copies in different location. I need a exact sequence unique long needed. If replication copy's same document is modified in more than one different location then replication conflict occurs. And also the sequence number has spoiled. New to notes developer says simply that silly problem. And some people used to say that this is easy but now only familiared with this. Only the people who have already faced this issue, they tell that I can not be solved. We have to manually resolve this.
Yes exactly, Project should be done with the customer requirements. No customer does like the rework.
Okay I come to point...
Before heading this issue we need to know about the "Replication conflict", "Replication", "Document Locking", "Developer's Responsibility [kidding]"
We have a lot of tool for handling this. But we are third party for customer. If we purchased tool from third party then we have a third party for our tool. so sixth party for customer . No customer needs that relationship. And also the license period and other things may conflict with our agreement.
Again we come with document locking. We need to enable the Allow document locking in database property. And we have to enable the master server in ACL of the database.These are features of document locking.,
if the document is not locked, the method places the lock and returns True
if the document is locked and the current user is one of the lock holders, the method returns True
if the document is locked and the current user is not one of the lock holders, the method returns False
if the document is modified by another user before the lock can be placed, the method raises an error
But the user does not want the hard reworking. So I analyze for the solution on this issue.
But still I have not clear idea about this. But complex way is there, That is, we have to check all the replication servers and while user tries to edit the document. For new document or sequence number creation we do not do it in replication server. Try to write a schedule agent for this.That will be the great idea. or Try to make a common sequence number format, Like Date + Location + Number , etc.,
For creating sequence number, funny this is too easy. Once fresher or new notes person needed, then reply me back