Re: debugging multiple forms

In the called form, place the code

        break;
in the trigger where you want the debugger to stop. Then you should be able to se the system-variables for the called form and your global variables. You wont be able to step your way thru the called form, so you have to write the breaks in your code before you run it (before you generate the .fmx file).

If this don't work, you could use message-boxes. Place a message(:global.global_var) various places in the called form.

-obv

On Thu, 23 Mar 2000 19:10:13 GMT, jim_wolfe_at_sra.com wrote:

> I may be missing something simple, but here goes. I'm developing a
>multi-form application using Developer 6.0. I'm passing data from one
>form to another using global variables. I'm having some problems in the
>interfaces and I'd like to trace the global values and their usage
>across the forms. I can run the root form in debug mode and trace its
>exection until it calls another form. The called form is a black hole.
>Is there a way to trace through the code in the called program using the
>debugger? I tried the debug package, i.e., Debug.Suspend. This
>suspends execution of the called form and I can see it in the Navigator.
>But, I can't see any of the trigger source code.
>Any help would be appreciated.
Received on Mon Mar 27 2000 - 18:39:00 CEST