Here’s the twist: only one particular client is getting the error. It happens on a call to db.GetDocumentByUNID. It works fine for every other user even when they are getting the same document. But one user seems to get this error (Document has been deleted) all the time.
-deleting cache.ndk does not help
-confirmed that the UNID in question is valid
-I don’t really want to run fixup because the db is huge and could take forever to run.
Any suggestions would be appreciated.
Subject: Document has been deleted error - again
If it’s a local replica, have the user close notes, open a DOS prompt, CD to the Notes program folder and type …
ncompact -i <path\database>
If it’s on the server, run it late at night. I found the best way to get by the Document has been deleted error is to compact with an -i switch, which will ignore the error, continue to compact.
Subject: Document has been deleted error - again
Are there any readers fields in the document and if so does this user have access to the document?
If you want to supress the error you can put ‘On Error Resume Next’ before the GetDocumentByUNID and then ‘On Error Goto 0’ after it.
Alex
Subject: RE: Document has been deleted error - again
There is at least one reader field, but the user definitely has access. The code is initiated indirectly from the document in question.
-The user opens the 1st document
-The UNID is stored as a enviromental variable
-A 2nd document is opened
-The 2nd document grabs the 1st document using the UNID (and updates it). The point of failure is here.
Subject: Can you post your code
Mike,
Can you post your code?
Alex