Would it be valid for our conduit to call an RPC at the start of its operation to perform this cleanup, or is the prefs database already going to be open by the time our conduit runs? If it's the latter, is there any way we can force the prefs database to be closed, even if it's been left open?
I'm just looking for a workaround, because even though the devices in the program have lots of third-party software, the blame finger gets pointed at us because it's always in our conduit that the crash occurs.
Unfortunately, the cleanup only works if done before the ExgMgr prefs are read.
You could loop through the open DBs with DmNextOpenDatabase, try to find the prefs DB using DmOpenDatabaseInfo, and then close it using DmCloseDatabase. I've not tried this yet, but it seems like a possible workaround.
-- Ben Combee, Technical Lead, Developer Services, PalmSource, Inc. "Combee on Palm OS" weblog: http://palmos.combee.net/ Developer Forum Archives: http://news.palmos.com/read/all_forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
