I have a database with some forms, and many documents created with those forms.
oneday I was add “doc.lock()” to the queryopen event and “doc.unlock()” to the queryclose event in one form, and then open a document(this document created after I modify the form) created with that form, the status bar display message “document successfully locked” or “document successfully unlocked”, it seem that everything OK.
BUT!
After I remove all the lotusscript code in queryopen and queryclose event, the “document locked” message still display in the status bar when I was opening the document created with that form!
I develop with domino for 6 years! I know many many bugs in domino or notes, lotus(or IBM) update the domino and notes continuously, R4, R4.5, R5, R5.0XXXX, R6, R6.0XXXXX, so many version, so many bugs! But they go-by it!
Subject: There’re so many BUGS with the “DOCLOCK” feature!!!
It sounds like you’re saying that your LotusScript code is still executing after you’ve deleted it. That would be surprising. But in that case, I don’t know why you refer to it as a bug in the document locking feature – it would be a bug in the Domino Designer LotusScript editor/compiler. I’ve never heard of such a problem. Did you try running with the debugger on, to see where this code is that’s executing? Are you using store form in document?
If there is not LotusScript code running, then possibly what’s going on is your use of the Lock method has deposited an extra field in the document which instructs Notes to lock the document automatically when it’s opened/edited. Check the document properties. I don’t know whether this happens or what the field name might be, but it’s a logical thing to look for,
Subject: RE: There’re so many BUGS with the “DOCLOCK” feature!!!
yes, I turn debugger on, but debugger window did not appear, because I has been remove all code in queryopen and postopen event
and then, 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 time, the designer’s lotus script code editor will automatically delete your newly entered code after you click save button in toolbar. This is problem(or bug?) I first meet in R6 initial release version, and I hope lotus will resolve this “problem” in future update, BUT, after so many update or “critical fix pack”, in newest replease 6.03, this “problem” still presence.
Subject: RE: There’re so many BUGS with the “DOCLOCK” feature!!!
As I said before, possibly what’s going on is your use of the Lock method has deposited an extra field in the document which instructs Notes to lock the document automatically when it’s opened/edited. Check the document properties.
As for the problem with edits vanishing in the LotusScript editor, this is a well-known problem which has been discussed several times in this forum. Last I heard nobody has been able to reproduce it reliably – it just seems to happen at random – and so it’s very difficult to find the cause. If you can tell us a series of steps that causes the editor to get into this mode, we would be very very happy to hear it.
Andre Guirard
IBM Lotus Software
Enterprise Integration Team
Subject: RE: There’re so many BUGS with the “DOCLOCK” feature!!!
yes, I turn debugger on, but debugger window did not appear, because I has been remove all code in queryopen and postopen event
and then, 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 time, the designer’s lotus script code editor will automatically delete your newly entered code after you click save button in toolbar. This is problem(or bug?) I first meet in R6 initial release version, and I hope lotus will resolve this “problem” in future update, BUT, after so many update or “critical fix pack”, in newest replease 6.03, this “problem” still presence.
Once enabled, you will find that every time you edit a document, the status bar indicates, “Document successfully locked.” Likewise, when saving/closing a document, “Document successfully unlocked” is written to the status bar. This requires no extra steps for your users. Behind the scenes, whenever the document is put in/out of edit mode, two fields are written to: $Writers and $WritersDate. The first field is a read/write access names field, the same as an AuthorNames field. The second field is a time/date stamp. These fields are used to let the system know that the document is locked. When unlocked, these fields are blanked out.
