>David Fedor wrote:
> > Fascinating - so if you run it under POSE exactly the same way, except that
> > you're not connected with the debugger, you don't see the error?
This happens for me, too! My guess is that the debugger locks down my
code, etc. BEFORE exiting the currently running app when I hit
'debug' thus making POSEr think that the currently running app has
left records locked... on exiting my app, then the code is still
locked and thus the error occurs again. But I am probably just
talking out my a** like normal ;)
Alan Pinstein
Synergy Solutions, Inc.
http://www.synsolutions.com
1-800-210-5293
