Is there anyway to know if there are more than one user viewing or editing same document
server rel 5
thanks
Subject: How can I know more than one user viewing same document
To simulate doc locking in R5, you can put a computed field on the form which was used to create to document. In the Queryopen or Postopen events, place a script to check if the field contains a certain value “1” open for editing, “0” open for reading. When an user opens the doc, the script checks to see if the lock field has a value, if the doc is already open by someone else, the field will contain either a “1” or “0” value or some other value. If the field contains “1” (for example), he can receives a popup message that the document is open (for editing for example) and he can only view the document and the script would force the document into read mode (Source.EditMode=false), if the field is empty when he opens the document, the script then would set the field to “1” and save using backend classes and optionally you could also have a names field that contains the name of the current editor of the document, so the next person to open the document would receive a popup message saying that a certain person is already editing this document and would show who it is. Whe the current editor closes the document, the script would reset the field(s).
Subject: …some suggestions…
In Rel 6 you have the ability to Allow Document Locking in a database, it`s not there in Rel 5.The purpose is to prevent two persons editing the same document at the same time, and it works.
Regarding two person veiwing the same document at the same time…well…system´s working as designed I guess? 
Regarding Repl/Save conflicts, dont delete the main document. To prevent them is thougher, keep the number of persons who are able to edit a document to a minimum.
Subject: How can I know more than one user viewing same document
Maybe http://www.xetrion.com can help you.
Subject: RE: How can I know more than one user viewing same document
As a previous posting mentioned, edit locking is native to R6. Read locking, however, falls under the heading of Document Management, and Domino isn’t a document management tool. Although such features can be coded in using PostOpen and QuerySave, such techniques are not foolproof, and therefore not sufficient for a high volume or high reliability implementation. In these cases, you would be well advised to use the correct tool for the job. Lotus, of course, would suggest you examine the favorable cost/benefit ratio of Domino.Doc – er, I mean, “Lotus Domino Document Manager.”