Hi, You NEED to lock your code into memory via MemHandleLock.... If you don't and the OS calls your app for the alarm callback, after the device's cache has flushed the OS is going to call random memory -> crash...
RLock does lcoks with MemHandleLock (imo, you'd need to ask Resco for exact details), but I wouldn't recommend using it or assuming that your users will :) RLock is nothing but a bandaid repair for bad or outdated code, imo... If you are programming for an NVFS device, do your users a favor and lock the resources yourself ;) ~Ryan On 1/23/08, Sagar <[EMAIL PROTECTED]> wrote: > > Hi, > > All the code that I access during my alarm is in my segment 0, which I > assume I have access to during display alarm launch code and dont need to > lock them (Correct me if I'm wrong). > > I read about DmProtectDatabase and it said one sould protect it in app > start > and unprotect in app stop. Sould I protect and unprotect the DB in start > and > end of all launch codes ? > > >>Also, make sure you open your application database, & make sure to open > it > >>in leaveopen mode. > I open my 'data' database when I need to write to it and close it soon > after > that - once during every alarm. Do I need to open in leaveopen mode then ? > > I still wonder wat Resco Backup/RLock does in special to Lock my app ? > > Regards, > Sagar -- Thanks and best regards, Ryan Rix TamsPalm - The PalmOS Blog Jasmine Bowden - Class of 2009, Marc Rasmussen - Class of 2008, Erica Sheffey - Class of 2009, Rest in peace. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
