Thanks to Eduardo for the link to Ben Combee's article. I also read the follow up: http://palmos.combee.net/blog/TheNVFSFilesDmSyncDatabas.html
These two blog entries are worth the read although it is important to note that this is old info, i.e. NVFS has been modified since the original deployment in the 650, T5 and E2. My problem is that majority of our users have E2's. The rest have a mix of T/X, Z22, 680, 700p and 755p. NOTE: Ben says, "Databases are written back to flash memory on several occasions. First, a database is written when it is closed. Second, they are written when the user puts the device into sleep mode. Third, they are written on a call to DmSync or DmSyncDatabase. A soft reset of the device will not commit pending changes." If a soft reset does not commit pending changes, does that mean that the cache is purged and the temp data that was not synced to the Flash is lost? Or is the data still in cache waiting to be used? If the data in the cache is not synced or cleared from cache then contamination that caused a crash could persist. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
