I have a form with over 255 fields. How can I see more than 255 when debugging LotusScript? I am working with Lotus version (6.0.1).

I am not aware of any limit to the number of field you can display in the debugger, and I could not find any reference to this limit at
Northern Collaborative. I'll take your word for it, but I would advise you to verify that you are not just having a scoping issue.

There are, of course, a number of undocumented limitations in the debugger. Chief among these is that it forces us to even think about the concept of displaying 255 fields. I had a chance to chat with the fellow over the debugger several years ago at LotusSphere. I asked him why in the world the LS debugger forces us to navigate through all those hierarchies instead of just providing a watch window. After explaining to him three times what a watch window is, he got very exited and said "Oh, that's a good idea!" Yes, and it was a good idea when Borland put it in the debugger for Turbo Pascal 3 in 1988! Do they actually USE Lotus Notes at Lotus?

Download this free guide

Download: IT certifications that stand out

Are you looking to advance your career? Expand your knowledge? Boost your credibility? Our editors put together this complimentary 19-page guide on everything you need to know about obtaining an IT certification—with special attention given to cloud and desktop certifications.

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent.

By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

None of that is going to help you of course. I am going to assume, however, that you are actually primarily interested in fewer than 255 fields in a given debugging session. I recommend that you create a "Watch" variable or two to help you in your debugging. A "Watch" variable is the name that I use for a variable that exists for no purpose other than so I can look at it while debugging.

Often, I create a string "Watch" variable that contains summary information from several other variables. This is especially handy when using a STOP statement to bring up the debugger when a piece of code first gets hit, so you know right away where you are in the process.

In your case, you are interested in fields on the document, so there is a "trick" you can exploit. Create a WatchItem as NotesItem variable, and then Set it to Doc.GetFirstItem("FieldNameOfYourChoice"). NotesItem variables store a reference to the actual element within the document's Items collection. So when the field (item) changes on the document, the NotesItem that has been set equal to it changes too and vice versa. In this way you can create several "Watches" and watch them change in the debugger as the document's fields are updated.

0 comments

Register

Login

Forgot your password?

Your password has been sent to:

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy