In my appliation, two users use an action button to “archive” status ‘CLOSED’ documents to a different database. The users have a view showing the documents needing to be archived and use an action button which runs an agent to copy the documents to the ‘closed’ database and then delete them from the original database.
Recently, one of them has been receiving the message “Notes Error : Cannot remove NotesDocument when instantiated by NotesUIDocument”. It doesn’t happen regularly, the second user never seems to get it, and I can’t seem to recreate it!
The posts about this error say it occured when using the preview pane, my users never use the preview pane. It was also supposed to be fixed in 6.5.1, we’re at 6.5.2.
Does anyone have any ideas what could be causing this? I can post the code if anyone thinks it would help. I just haven’t seen this before now.
Thanks!
Deb
Subject: Notes Error : Cannot remove NotesDocument when instantiated by NotesUIDocument
I ran into this as well with the version that it was suppose to do this with. What happened was the user had a preview pane open, but it was opened slightly, you couldn’t hardly tell at first glance.Verify that it is indeed all the way closed.
Just an idea.
Subject: RE: Notes Error : Cannot remove NotesDocument when instantiated by NotesUIDocument
Thanks for the suggestion, Chris. I’m using framesets in the db and didn’t give a way to even show the preview pane, so I don’t think that can be the problem. Thanks again.
Subject: RE: Notes Error : Cannot remove NotesDocument when instantiated by NotesUIDocument
Sometimes, IBM/Lotus introduce regressions into newer versions of the client that we all thought were long gone. If the answer is not the preview pane thing (and you are absolutely sure of this) then, this bit from older versions (R4!) may provide some insight into this error message:“This bug occured if a document was open in a frame, and then that same document was opened full screen for editing.”. This would suggest to me that user one is editing the document in a different manner than user two, and thta it is causing this error. I hope this helps a bit…