> I am working on a program that does backup up and restore without using > conduits. When I am transferring files to the device, I want to skip any > open databases, or loaded shared libraries since it seems to be bad to > overwrite a datebase being used.
It's definitely something to avoid. :) There are really two issues here: 1. How to detect databases that can't be overwritten. I'm not sure why you need to detect this situation. Could you get away with just handling the error you get back from DmDeleteDatabase (in your delete callback for ExgDBRead)? You can't overwrite databases that are open or protected. Shared libraries aren't the only databases that can be protected. You can enumerate the open databases using DmNextOpenDatabase. There's no way to check if a database is protected, but you'll find out when you try to delete it (in order to overwrite it). 2. How to minimize the number of databases that can't be overwritten. If you can have the user do a no-notify reset (hold down up button while inserting reset pin), there will be fewer databases that can't be overwritten. This will disable IrDA, so you won't be able to use IrCOMM to communicate with the desktop. I don't know if this is an issue for your backup app. Be sure to have the user do a regular reset after the restore is complete. - Danny -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
