I saw the same problem. After going back and forth with Palm DTS for about two weeks, we solved it by placing a DmSyncDatabase() call after *any* record operation. This didn't seem to impact the performance too much.
Note that putting a single DmSyncDatabase() call after DmCloseDatabase() did not fix the problem ... we had to call this API after every record opeartion, unfortunately. Be sure you do the appropriate tests that the trap actually exists for this API before you call it! It will probably crash during runtime if called on any non-NVFS device (and rightfully so). Be sure to install the latest Palm SDK to 'see' this API. -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/
