Replication or Save Conflict

Before I start, I know this problem has been posted many times before, but there has not been a reply of how to stop it from happening.

I have a database that runs on the web.

When I create and save a new document (by using a submit() command) an agent runs (specified in the WebQuerySave) it gives the form the next sequential number (using a LotusScript Agent) which contains the following command :

//mydoc is the current document

mydoc.save false, false

This works fine when creating a NEW document.

Now, when I go into the the record, change some fields, and save the document (same way) I get the dreaded:

Replication or Save Conflict

in the view.

I dont want to remove the entry as this is the latest entry, and I dont want to filter the entry out. All I want to do is OVERWRITE the document with the latest one.

Is there a reason why this is happening? and how can I stop it from happening.

Many thanks for your replies

Subject: Replication or Save Conflict

The reason for the conflicts is the mydoc.save command you issue in the WQS agent.

You don’t need to do a save in the WQS, since the document will automatically save unless you explicitly put a SaveOptions = “0” on the document. The result is that the WQS agent fires when the document is submitted, it saves the document, and then the document is saved as a result of the submit action, creating a conflict.

/Peter

Subject: RE: Replication or Save Conflict

Thanks for the reply, that has cleared it up for me