It does quit.
Though yesterday I did experience the minimize to a small short bar (for
the first time ever)
At 12:40 AM 2/21/2003 +0000, you wrote:
>
>Dan,
>
>Just a quick thought, it's way past midnight here:
>
>Does TRACE actually quit or does it minimise itself? Over the last few weeks
>I've noticed that when certain EEPs run - and I don't what determines this -
>TRACE can minimise itself and appear just as a small bar somewhere on the
>screen.
>
>You can grab the corner(s) and re-size it and then continue as if nothing
>had happened. I have no idea if this always happened or if it is something
>new but I hadn't noticed it before the new patch. That's a statement and not
>a criticism or anything.
>
>Regards,
>Alastair.
>
>
>----- Original Message -----
>From: "Dan" <[EMAIL PROTECTED]>
>To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
>Sent: Friday, February 21, 2003 2:03 AM
>Subject: [RBASE-L] - Trace
>
>
>>
>> Hi,
>> In all the discussion about my code crashing, and possible ways to find
>> it. TRACE questions came up that are yet unanswered. Trace willl not go
>> far enough, or quits when I need it most. Any ideas how to get the info I
>> need to find my coding conflict? It isn't a memory issue (this machine
>has
>> one gig of ram, and quits at the same spot my small machines do), I have
>> placed Trace in eeps, and even used {shift} {ctrl} {f12} to start trace at
>> different spots, yet trace quits while inside a form The form is called
>> up, and that is the end of trace.
>> So, what are the limitations of trace? I really need to find this bug
>and
>> squash it.
>> Thanks,
>> Dan
>>
>
