A read-write database is imported from the expansion card using
VFSImportDatabaseFromFile. If changes are made to the database, the pdb
on the card is deleted, and the newly revised pdb in main memory is
exported back with VFSExportDatabaseToFile. However, when the app is
launched again, a subsequent call to VFSImportDatabaseFromFile results
in a data manager fatal alert "Record isn't busy". I have used
Insider.prc and the Simulator's database viewing capabilities to
confirm that none of my records are left busy. Various records have
appropriate dirty and/or deleted bits set. Inspection of the database
code confirms that all calls to DmGetRecord and DmNewRecord have
accompanying DmReleaseRecord calls. I do NOT get any other "busy
record" notifications (like "Records left busy in locked
unprotected...").
Is the data manager telling me that the record is busy, but shouldn't
be, or visa versa? What step do I need to take when modifying my
database to prevent the "Record isn't busy" notification?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
