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

Reply via email to