I'm afraid I'm not having much luck finding this problem. Every DmGetRecord/DmNewRecord has a DmReleaseRecord, and the handles are locked while used and not accessed after unlocking. No records are accessed from an closed database (and protecting the database on open didn't help).
Still the problem persists (and still it works in the Simulator). I didn't write the database code, so it's possible there's something funny there, but nothing obvious seems wrong. One other area I'm pondering is bitmaps. I have a lot of small bitmaps (card suits) embedded in my PRC that are loaded via DmGetResource. Since the resources are in my PRC, there's no DmOpen of any sort; I just call DmGetResource given the bitmap id, and lock the resultant handle. On exit, I unlock the handle and release the resource. Is this kosher, or do I need to protect the resources in my PRC somehow? I'm running out of ideas. Is there some way I can force this problem in the simulator? Finally, I'm a little alarmed by the statment "DmQueryRecord is safe to use again" from the Palm Developer Guide. My code uses DmQueryRecord -- is there a recommended alternative for the OS versions where this was (apparently) unsafe? Thanks for any ideas! Paul Close -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
