> Can you be specific on what kind of dm functions that > could accidentally make the database invalid?
That's a pretty open-ended question! One that I ran into myself, is that if you have a resource DB then there must be no duplicate resource IDs, or else the resource DB can't be installed via HotSync. My point was simply that I know this is possible, and if the database is one that your code generated, then almost certainly there is a bug in your code, rather than a bug in HotSync or the OS or etc, and you should focus on debugging your code, rather than spinning your wheels trying to find some way to install the database even though it's invalid. > DmCreateDatabase(1, "databasename",0,0,0); > Could it be that my database doesn't have a creater type etc... ? That would be the first place to start, anyway. You're supposed to give the database a creator id and type id, and generally the creator id should be the same as your app creator id, unless you need for the database to remain on the device if you delete the app. If you assign it the id's and it still doesn't work, keep working on it to find the additional problems -- there could be several not just one. One thing you can do to help test your code is create the database in POSE, exit your app, Export the database to a file, and then install the file back into POSE. It'll probably refuse to install the database in the same manner that HotSync does. > DmSetDatabaseInfo Depending on how you use that function, I suppose you could hose things. In general, if you're trying to avoid specifying things that belong there (as in the case of the creator/type ids above) then those would be the first places to focus on. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
