I have an action on an existing doc in edit mode which creates a new doc (different form) and populates it with some values. I want to debug the querysave of the new document but can’t seem to get the debugger to kick in on any of the script in the new doc.
If I have debugger on when I open the existing doc and click on the action, debugger starts and I can follow it all the way through creation of the new doc, etc. until it exits the script. So now I still have the existing doc open and the new doc is now open also (but not yet saved). If I then save the new doc, the debugger never shows even though I have script in querysave and postsave.
I have tried waiting until the new doc has been created before turning on debugger but that didn’t work either (which I expected).
Any ideas?
Subject: can’t enter debugger on new doc when created from script in another doc
Me too.
Well, my issue is a little different. I have a rather long agent that eventually opens a new document. This new document has some code in the “post open” event. 95% of the time the debugger will open to the agent. 5% of the time the debugger will open to the first line of the “Postopen” event (skipping the agent altogether).
The cool thing about opening to the “Postopen” event is that the debugger is now running along with the new form. It will step through the code in buttons, and all “QueryXXX” and “PostXXX” code. (Which is what Christopher is looking for.)
Here is the problem. I can’t seem to find what triggers the debugger to skip the agent and go directly to the “Postopen” event. It seems to be random. It seems to happen more often if it the first thing I do after my PC reboots.
By the way, putting a “Stop” in the Postopen event will be completely ignored if the debugger starts in the agent. It seems that if the debugger starts in the agent it (the debugger) is instructed to close when the agent completes.
Any body else run into this? Have any of you gurus figured this one out?
PS: Version 6.5.1
PSS: Christopher, Sorry this doesn’t answer your question. But I think the two issues might be related. If we could either keep the debugger from terminating or force it to respond to all events it would fix both of our problems.
Subject: Debugger doesn’t stop in script though it did 30 mintues ago…
Same issue - script creates a doc, can’t get the debugger to stop in the script of the new doc but it was a little while ago! Change some of the code and it is now generating an error but the debugger no longer stops there. If I comment out the code with the error, debugger still WON’T stop there.
What gives??? I’ve had this happen before but can’t recall what caused it or stopped it.
(7.0 BTW)