i found dmModeLeaveOpen, which explicitly prevents the database from getting closed by SysAppExit. this is exactly what i want, EXCEPT that i've grep'd thru the OS source and i can't find any code that resets the open counts of all databases to 0 on a Reset. can someone tell me for sure if a Reset will fully reset the open counts of all databases to 0, even ones opened with dmModeLeaveOpen? it seems like it would have to, but since the published OS source doesn't contain the code that does this, i am questioning myself. i just don't want to be leaking DmOpenRefs after a crash or Reset. all other scenarios are definitely under control. ----- Original Message ----- From: Scott Johnson <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 07, 1999 1:23 PM Subject: Re: database is getting closed for me?? > Chris Antos wrote: > > i can't find who calls SysAppExit. does the compiler/linker > > stick in an implicit call to SysAppExit in the app's exit code? > > Yes. The CodeWarrior startup code calls SysAppExit at the very end of > __Startup__(), which is your app's true main function. The source for > this, under the CW R5 directory in Windows, is -- > > .\Palm OS 3.0 Support\Runtime\(sources)\PalmOS_Startup.c > > (I assume GCC startup code would be almost identical.) > > -slj- >
