David Jones a �crit : > On May 19, 2004 02:58 pm, you wrote: > > At this point, by far the most current error I get in POSE either > > testing or running the Gremlins is "Records left locked" or "Records > > left busy" in closed unprotected DB. > > > > As I don't use DmGetRecord at all (preferring DmQueryRecord, even when I > > call DmWrite later), how can I en up leaving records busy? Can this > > induce problems when I re-open the DB, like when trying to accesss a > > busy record? > > I have noticed one thing: the "locked" attribute is persistent. > > Run your app, which writes to the database and locks a record, and then exits > leaving the lock. Then exit and run again, this time doing NOTHING that > writes to the database. The warning message will still appear on exit, > because the lock bit is still set, and nothing has yet cleared it. > > The only way I know of to reset the lock bit is to delete the database and > start over. > > Now for my questions of the experts: > > 1. Does DmAttachRecord() lock the record? What other calls (besides > DmGetRecord) lock records? > 2. Does calling DmUnlockRecord() on an unlocked record lock it unexpectedly? > 3. Is there a less drastic way to reset the lock bit on record(s)?
What about the busy bit? Is it only set by DmGetRecord? Or does DmWrite set it too? Is there a good text on that? It's becoming a pain because when running Gremlins, this comes up all the time and minimizing failed Gremlins often leads to these locked/busy errors instead of reaching the initial crash :( -- Luc Le Blanc -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
