Steve Ellenoff wrote:
> I'm working on an inherited project and there's a bug I'm trying to
> track down where a cursor is expected to be open as the app is
> exiting, but it's closed already. Easily handled by just bracketing
> the code with IF USED("tempout"), but I want to find out why this
> used to work before and no longer does.
>
> In the watch window I put: USED("tempout")
> and placed a breakpoint on it.
>
> Starting up the app, the breakpoint fires exactly where the cursor is
> created as it should.
>
> However, closing the app down, the break point stops on code
> un-related to this cursor at all.
>
> My guess would be that it is not showing where/how the cursor got
> closed because the line that closes it is the last line of some
> object, and since the object is no longer in memory, the breakpoint
> can't stop there? Just my guess, as I don't know why else.
>
> Anyone have a suggestion how I can track this down?
>
Trace into that "un-related" section...there's gotta be something.
Perhaps a DataEnvironment closing it, another class object that's got a
CLEAR ALL or CLOSE of some sort, etc. Is the cursor in the Default
data session or a Private data session?
--
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutions!"
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
