On Fri, Jan 23, 2015 at 4:06 PM, Patti Jakusz <[email protected]> wrote:
> I never realized you could embed trace in a command file. I always used it
> from the R> prompt.
>
> I had set echo on and output filename.txt with screen, and it really
> didn't tell me anything. It just gave me the "No whiles or Ifs" that I
> mentioned below.
>
> Now I know how to embed the trace.
>
>
Patti (and others),
In complicated forms, with lots of EEPS I often do this:
- Locate a button
- Set Caption to "trace"
- Set component ID to "traceButton "
- Right-click it and check "Hide on startup"
- In the On Click EEP:
IF (CVAL('TRACE')) = 'ON' THEN
SET TRACE OFF
PROPERTY traceButton CAPTION 'Set trace ON'
ELSE
SET TRACE ON
PROPERTY traceButton CAPTION 'Set trace OFF'
ENDIF
RETURN
- In Form Settings/On After Start EEP:
IF (CVAL('computer')) = 'my-laptop-name' THEN
PROPERTY traceButton VISIBLE 'TRUE'
ENDIF
SET VAR vShowTraceButton TEXT
IF vShowTraceButton = 'true' THEN
PROPERTY traceButton VISIBLE 'TRUE'
ENDIF
Then, when I am using a form I can turn trace on and off by clicking the
button. If I'm on somebody else's computer, at the R> prompt I can type...
SET VAR vShowTraceButton TEXT = 'TRUE'
... and I get to see the button even though they do not normally see it.
Bill
