Thanks for the idea, botchy or not. As long as it works. Still confused a bit though...
My user reported no app db casualties when a call came in while in "browse mode"; only when in "drawing mode" (i.e. in an EvtGetPen loop). Yet, app dbs were opened at startup, i.e. in both modes. Plus, I have placed so much db validation code in my app at startup that, were db corruption to occur, an alert would pop up. User reports a system wide crash after the call, when he attemps to restart my app. So perhaps it is prefs corruption, something I am not validating enough apparently (other than through the obvious prefs size comparator). Need to bullet-proof this code some more. In conclusion, really wish I could simulate an incoming call notification from outside my main app event loop. That would be the proper key to debug this thing. In any case, thanks for your help. Much appreciated. Cheers Alex -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
