Breaking out of RecordLock...
Ken Ray
kray at sonsothunder.com
Wed Feb 18 15:59:46 CST 2004
> >That's exactly what we've been doing, which is why we find
> it odd that
> >a cursor might be left "open"... we've been very careful to
> create and
> >remove cursors in the same handler. Our program is quite
> large, though,
> >with dozens (if not hundreds) of SQL calls, so tracking this
> down will
> >be hard.
>
> Have you tried writing a scavenger script? A handler that goes
> through all objects of a selected stack, fetches their script, and
> finds all valentina calls, reporting them in a sequence (or reporting
> only selected ones)?
Sounds like a good plan.
> Another thing to check is whether you do error checking after each
> valentina call. May be you do have a close request but it has a typo
> or something. If the error is not detected, the cursor is left open.
> Similar scavenger script can report these as well (particularly easy
> if a central error handler is used).
I already channel all Valentina calls through a central "wrapper"
handler that checks for errors before processing, so at least I can rest
easy on *that* account.
:-)
Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/
More information about the Valentina
mailing list