Cannot debug Lotusscript (debugger disabled?)

One of my clients have an application where it has been impossible to execute the Lotusscript debugger. As usual, I turn on the Lotusscript debugger, then open the database and click on a button that executes the lotusscript code that I want to debug. When I turn on the debugger and open the database I see a window that opens and closes really quick and I suppose that is the debugger console, but I never see the code I want to debug. I know it is executed, but I just don’t see the debugger. I even tried adding a forced error and even when I get the usual “Object variable not set” I still don’t see the debug console.

It’s weard because even if my code has a dialog box I get the typical message of “Cannot debug in a dialog”, the debugger is runnign but I just don’t see the console.

I am new with Lotus 8.5.2, but I’ve been working with Lotus 5,6 and 7 for almost 10 years. If I try to open the same database on local or using Lotus designer 7 I still have the same problem. Same happens if I try the same from another workstation.

If I try to open another database (for example my mail database) the debugger works as usual, no problem there. The thing is I cannot debug lotusscrip on this database.

I wonder if there is a way to disable the lotusscript debugger on a database. I checked and the design of the database isn’t hidden, after all, I’ve added code to the application.

I’ve called Lotus support in Spain and they told me there must be something wrong on the database but it’s weird since I’ve never seen this in more than 9 years working with Lotus.

Haven’t found any similar issue on the forums for versions 5,6,7,8 and 8.5. I wonder if anybody here can help me at all since without the debugger I’m practically working with a blindfold.

Thanks in advance.

Subject: Better LotusScript debugging…

…hasn’t been a priority of the development team of late. However, it might be worthwhile to call Lotus Support and send them a copy of your database to see where the problem is. It doesn’t sound like a recent regression.

There are things you can do to figure out what’s going on without debugging, which are discussed here: Debugging Domino Applications part 1 and part 2 .

  • Andre Guirard, IBM/Lotus Development

Useful blog: Best Practice Makes Perfect

Subject: Strange debugger behaviour

Well… at the end to make the debugger work I had to remove an embedded view and a subform that I was using. This subform sometimes opened a dialog and I guess that was one of the problems.

So after removing the embedded view and the subform I am able at lest to debug the buttons I had problems with. I guess I’ll have to do the same everytime I want to debug this applications.

Thanks anyway for your help.

Kind regards,

Luis