The database having the "open" attribute set is mostly irrelevant. It being present in the list of open databases is relevant, This list is erased at soft reset. So fileZ is not lying, it is just telling you something which is irrelevant to your situation.
On 1/26/07, Bruce Waters <[EMAIL PROTECTED]> wrote:
Thanks. Somehow my eyes have forever so far missed "seeing" DmOpenDatabaseInfo() listed in the documentation. However, now I'm confused. What Jeff said below is what I would like to be the case, and I've no doubt the misunderstandings are mine, but what they are so far eludes me. My app runs fine on POSE. It uses expansion card for permanent data storage. I've just got to the point where the VFS stuff for support of expansion cards is working right, and so now I'm beginning to debug on a real Dana for the first time. I've run in crashes the cause of which I've not yet worked out, and they leave databases open but shouldn't have as I have an abort function which is supposed to close them all amongst other things. (At least inspection on the Dana using FileZ / Details / Attr tab shown the Open checkbox ticked for the databases). Point taken about no crashes allowed for a user, but it would help me to speed up the debugging cycle if I can avoid having to close the open databases using FileZ by doing it with some code. A soft reset on my Dana doesn't do it. After doing the soft reset, if I check the same databases again using FileZ, they are shown to me as still open. Presumably FileZ is not lying, or am I missing something? --Bruce
-- Best Regards, Dmitry Grinberg Software Engineer, http://PalmPowerups.com (847) 226 9295 AIM: DmitryGrinberg MSN: [EMAIL PROTECTED] ICQ: 165589894 Y! IM: dmitrygr2003 -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
