I recently had to remove the Dm calls in my app and use preferences instead. When I was using the Dm calls things would work well but the moment I try a hotsync or launch another app, I always get a fatal reset. I had my DBOpenRef (?) variable in the same source as my PilotMain and I used extern references to it in other source files. I think I must have spooked the OS using a global variable as I think the launch of the other app might have fooled the OS into looking for something that was no longer there - just a hunch.
If I want to use a global variable for my database reference then what should I do to ensure the fatal reset does not occur. As I say, the problem disappeared once I removed all the Dm calls. I was toying with the idea of opening and closing the database around every Dm call I want to use, but is that inefficient? If nothing else, it makes for ugly code. I'm trying to work out what to inbetween launch codes.
I'm not sure keeping a database open across runs of your app is really a good idea. Why not open it when the app starts and leave it open til the app closes? And if your app is opening and closing very frequently... you might try running it that way to see what the performance is. If it is too slow, Prefs might be right or maybe feature pointers.
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
