"DOC LOCK" feature again!

I wad upgrade my Notes Client to 6.5, but then server still 6.03.

There’re many many new topics here everyday, just one day, my post has been fall into oblivion.

In last weekend, I was done an deep test.

I add LS code to form’s QueryOpen event:

call doc.lock()

and add LS code to form’s QeryClose event:

call doc.unlock()

Then open a document created with this form, after the document opened, status bar display a message: “document successfully locked”.

I close the document, status bar display a message: “document successfully unlocked”.

It seem everything OK.

now, I remove all code in QueryOpen & QueryClose event and open same document again, the document should not be locked, but after document has been opened, “document locked” message still display.

I turn debugger on, but debugger window did not appear, of course, there is no code to debug.

I type code:

if 1 = 10 then

call doc.lock()

endif

in queryopen event to test. As you know, the “call doc.lock()” statement will never run. In debugger window, I click “step into” button to debug the code, “call doc.lock()” not run , but “Document successfully locked” message still appear after queryopen event! If this is not bug, what the hell is it?

By the way, I tell you another serious bug in R6.0X, im some case, the designer’s lotus script code editor will automatically delete your newly entered code after you click save button in toolbar(After close the designer and reopen it, this “problem” gone, but some day, “I will back!”, the bug said.). This is problem(or bug?) I first meet in R6 initial release version, and I hope lotus will “terminate” this “problem” in future update, BUT, after so many update or “critical fix pack”, in newest replease 6.03 or 6.5, this “problem” still presence(“he” is back!). The LOTUS says, “My BUGs will go on!”, right?