We have a database which has been in operation for quite some time. That database has a form which contains a couple of embedded java applets (used to display graphs).
Historically, this has worked as expected with no negative ramifications… until now.
We have two users who are trialling the new 8.5.1 Lotus Notes client. Whenever they open a document based on this form, that document’s properties indicate it was last modified by them when they close it. The date/time stamp reflects the time they closed the document. All this, despite the fact the document was never even placed in “Read Mode”.
We tested this operation with R6.x, R7.0.2, R8.0.2, & R8.5 clients, and none of these clients exhibited the same behaviour.
We have tested with the Notes client preference - “Enable java applets” - both checked & un-checked (just in case, although I don’t believe this has any bearing within native Lotus Notes apps).
Has something changed with the 8.5.1 client that would explain this behaviour? Is there something we need to change to ensure this does not happen?
This is a distributed database, and we obviously cannot roll out the 8.5.1 client if it means we are going to end up with thousands of rep/save conflicts.
Any assistance would be greatly appreciated!
T.