Hi all…I have this odd problem with the Debugger and came across another user with the same problem but no solution. The thread below describes the problem, does any one have a fix for this?
Thanks / Arvind
I am trying to run my script in debug mode so I can check it line by line. Except it won’t kick in.
The script in question is in a form action that calls a sub from a script library. When I select the button it just runs the script rather than going into debugger.
The debugger is definitely turned on and I have tried putting ‘Stop’ all over the place but it just ignores stop. I know the script is running as I’ve included a messagebox.
Has anyone got any ideas? This is driving me nuts!
Have you tried closing the form/database, then reopening and running with the debugger already on? Debugging sessions only apply to objects open after the session has started. (Conversely, turning off the debugger won’t take objects open under a debugging session out of debugging mode.)
Tried it but the problem doesn’t go away. The action that calls the script library sits witin a form. After I start the debugger, when I click on a document on the view, I do see the debug screen but I press continue to move on…since I need to debug the action button within the form. Now when the form loads and I click the action button, the debugger just doesn’t start. Has it got to do with the Script library loading up before the form loads? I’m lost here.
Clicking “CONTINUE” tells the debugger to run through the code WITHOUT stopping (unless you have breakpoints set up from aprevious session) - you should click on “STEP INTO” to run through the code line by line…
I realize…but I do that only to get the form to load. Thereafter, I click the action button, which is what I want to debug and the code executes without the debug window. Anyway, I’ve tried stepping into the code just to get into the form but that didn’t help either. The debug window did not show up after I clicked the action button.
Put a STOP command in your code where you want to start debugging.
Then, when you press CONTINUE when the form opens, the script will continue until it hits the STOP statement, and allow you to debug from that point on.
The CONTINUE action really turns debugging off until a stop is encountered, or a new object is opened. Clicking on a button in the form is still considered part of the form, and won’t reactivate the debugger.
Now thats a trick I haven’t tried Graham. Looked up the help file and couldn’t find an example of how to use a STOP statment. Could you give me an example.
' Prompt the user for the file Dim w As New NotesUIWorkspace
Dim file_name As Variant
file_name = w.OpenFileDialog( False , "Select CSV data file" , "" , "C:\LNET" )
Stop
If Datatype(file_name) =0 Then
Msgbox "No file selected"
Exit Sub
End If
Dim db As NotesDatabase
Set db = session.CurrentDatabase
Thanks Graham. Tried the Stop statement and that didn’t work either. I’ve resorted to using message boxes within my code and am working around the problem. Phew!! Any other ideas, please let me know
Does the problem persist through a stop/start of all of the Notes clients? Through a reboot? (I’ve seen some strange assertions of “binary squatters’ rights” by Notes sessions that have been allowed to live in one area too long.) These are WAGs, not Expert Opinions.
I am on R654 on XP and I have the same problem with 1 db. Step1 turn on debugger. Step2 open database. Step3 open selection in navigator, this has a stop that works so I just step thru it. It open a form to be filled out ( strange #1 ) It does not actually give you the form, it become an Icon in the top task bar. Step4 use button on form to pick a person ( Function language code ) Step5 use a second button to execute a call to a script library to execute script code to go and get the person-data. There is a stop at the begining of this code. IT DOES NOT STOP.Strange #2 This works on other database on my desk top. Strange#3 this behaviour in the offending database does not happen in my fellow developers computer. R654 was reinstalled. NO CHANGE…Fixup run, new copy made, and design/tools/recomplie script run. All to no avail.