Thanks to those of you who responded. In all cases you suggested that the dmHdrAttrResetAfterInstall bit was set in the PDB, which turns out not to have been the case. The culprit, in fact, was the dmHdrAttrOKToInstallNewer bit, which I was setting in order to allow a new copy of a database to overwrite an old one. It turns out that: a) If I head read the documentation (all 1 line of comment in datamgr.h) I would have seen that the bit allows overwrite of an _open_ database. You can always overwrite a closed one, so it isn't really necessary in my case. b) It also seems to force a reset. All of the time (I was wrong about it being sporadic.) I thought you might like to know. Thanks again, - jim berry Jim Berry wrote: > I've written an app that imports data via .PDB databases that > get written by various external applications. > > Frequently, though apparently not always, HotSync'ing one of > these DB's onto my pilot results in a "You must reset your > Pilot" message on completion. > > Is there something subtly wrong with my PDB's?
