I believe the DmSyncDatabase() call was effective at preventing disappearing PDBs when placed after DmWrite(), however I don't recall if it was placed after reads as well. I'm going to guess the latter is not necessary.
Though speaking of data manager reads, this reminds me of another OS bug I stumbled across that Palm DTS had to help out with. On a T|X, calling DmResizeRecord() would consistently cause the OS to crash in one section of code. The solution from Palm DTS was first to call DmQueryRecord() to pre-load the record (into the cache, I assume) and only then call DmResizeRecord() (the handle acquired from DmQueryRecord could then simply be disregarded, as no lock nor dirty bit was involved). This workaround solved the problem. -Jeff Ishaq Palm OS(R) Certified Developer -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
