I am trying to trace the steps that a routine that works well when executed from TCL but when called from a popup it jumps to the end of the routine and does nothing.

I would like to use the debugger to trace the steps that the routine is taking so I can take corrective action.

Thanks in Advance for all helps, hints, and insights.

Dale

In order to trace steps, the first thing you need is a really big magnifying glass and one of those Sherlock Holmes hats. It also helps if you can speak with a British accent whilst doing this.

Then, with the help of your cousin Oliver playing Dr. Watson, sneak around the code and try and find out things you shouldn't know. And just so you know, I already checked, Tiger does not have Kitty Carlisle burried in his dog house.

The other thing is to hire Jim Rockford. He never fails. Jim's my hero.

[email protected]

Are you calling the popup in code? If so, you should be able to place a debug in there.

If not, depending on how the program is loading, the (D) option at TCL will load the program right into the debugger.

It could be that the popup is killing a select list or some other status variable you need set.

Or do you not know how to move through the debugger?

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

Gary,

I just stepped through the debugger after reading your instructions. But I have one quick question…

How do I remove my foot from the monitor without bleeding to death?

Eric

a) The popup is called from within a routine to select various reports.

b) this works for other routines that I have been working on.

c)No I do not know how to use the debugger after all these years and I go back to revG. This is something I have avoided like the plague.

I look forward to your insights.

Dale

OK. Real simple.

In the line of code after the popup, place in the keyword

DEBUG

on it's own line.

This will take you right into the debugger. From there, you can start stepping through the program.

Entering H (or HM) if you are using a later version of ARev, will bring up the help screen. Try HM first, since it brings it up in a scribe window so you can see then entire text.

En allows you to step through lines. E1 will take you line by line.

ST will toggle display of the current source line.

B@ is helpfull if you are calling other programs, like MSG and do not or cannot walk through them. What you would do is enter

B@=MYPROG

substuting your program name for

MYPROG

. This will send you to the debugger whenever a specific program is executed.

B$ can be very helpful to jump through a code loop or around equates or something like that.

/varname

will display variables.

Vvarname

is better since it will display the record in a scribe window.

V

alone will show a popup of all the local variables.

This is probably enough to get you going to start.

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

Thanks!!

I will try this and let you know if I have any problems or concerns. I appreciate the concerns of the other waterbuffalos and their succint observations.

Dale

OK. First thing you need is a large mop and a very big bucket. You'll want to save all that blood. You're probably going to need it later.

Best idea I can come up with is to immerse the monitor into a glass blowing furnace. This will melt both the plastic and the screen glass so you will not get any more cuts or punctures. The extreme heat will be beneficial to any current bleeding as it will cauterise the wound to stop the bleeding.

Shame the debugger isn't object oriented otherwise you have sent a "remove foot" message to handle this for you.

[email protected]

View this thread on the forum...