I found it and it was my mistake. I was looking for missmatched DmNewRecord/DmReleaseRecord when it was a MemHandleLock on the record handle itself. After typing the first message I went back and matched the Lock/Unlock calls and that was it.
I should probably type up these questions and not send them for 1/2 an hour. I usually find the problem after explaning the problem in the email...
Thanks for the suggestion though.
Dana
Ben Combee wrote:
At 02:08 PM 5/14/2004, you wrote:
When my application quits I receive the "Record left locked in closed unprotected database" message. I understand what this message means but I can't find the database record I'm not releasing. Every DmNewRecord(...) and DmGetRecord(...) has an associated DmReleaseRecord(...). I'm pretty sure the index value isn't changed between these two calls. I'm also checking each MemHandleLock() for an associated MemHandleUnlock() but so far haven't found it.
Am I missing something here? Is there another mechanism that locks records that I'm not aware of? Is there any way to see which database has the locked record?
Are you using a multisegment app or using expanded mode with CodeWarrior? It's possible (but not likely) that the locked record is actually one of your code segments. Does this message appear only when debugging your application?
-- Ben Combee, DTS technical lead, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
