>From the evidence you give, I would suspect that you are doing something wrong in your handling of both the reset and sync notification launch codes. Perhaps opening a database exclusively and not closing it again? A good practical way to test this hypothesis is to create a custom build of your app that calls the same code you run off of the reset and/or sync from elsewhere (the find launch code is my favorite, as it too can run without globals) and see if you have the same behavior after running it here. An added advantage of this approach is that you can debug the code easily off of a find.
Of course, if you aren't responding to the sync or reset launch codes, my hypothesis is pretty much busted. -bob mckenzie, palmsource pdx -----Original Message----- From: Romain Eude [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 10, 2002 11:26 PM To: Palm Developer Forum Subject: Fw: application crashing on 1st run after sync... I have a program that talks to a springboard and then writes the content of a large structure to several records within a PDB file. It first opens/create a PDB file, then performs several DmWrite, then closes the PDB. When I run the program, I get the following strange behaviour : * I hotsync, * I run the program reaches its end and exists, there is a 'fatal exception' -> I reset the palm, * I run the program many times in a row and it does not crash.... .... * If I hotsync, the 1st time I run the program, it will crash and after a reset it will work fine... What is wrong with what I am doing ? Romain. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
