Hi,
it happens in DmCloseDatabase() if
DmGetDatabaseLockState(dbR, &highest, &count, &busy);
yields highest > 0. You should be able to find the problem by inserting a
few test calls to DmGetDatabaseLockState.
Regards,
Jan Slodicka
P.S. You can find some explanation for similar problems in Palm OS 4.0
Limited Sources. (Available at PalmOne.)
----- Original Message -----
From: "Luc Le Blanc" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Wednesday, May 19, 2004 8:58 PM
Subject: Records left locked or busy in DB
> 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?
>
> Regarding locked records, how can I tell which records are locked? There
> is no such Record Attribute Constant defined. I gather I must have a
> MemLock( recordHandle ) not matched by a MemUnlock somewhere. Or can
> there be another reason?
>
>
> --
> Luc Le Blanc
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
