Thank you. I'll attempt to reconsider the structure of my routine's logic in light of the information that you were kind enough to provide.
----- Original Message ----- From: "Dean Gahlon" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[email protected]> Sent: Thursday, November 17, 2005 4:59 PM Subject: Re: Database Sorting Problem > On Thu, 17 Nov 2005, Del Ventruella wrote: > > > The rec4 was left over from an earlier attempt. I had thought that > > MemHandleLock was only necessary to copy data from a chunk reserved for a > > database record to non-database memory when the copy occurs. That is the > > reason I allocated memory space to multiple rec# variables. I locked the > > database memory space again before writing non-database memory contents to > > database memory. > > > > Thank you for your response. > > > > Just to be clear, this idea about MemHandleLock is completely incorrect. > MemHandleLock is used to lock a handle in place so that it can be > referenced, and has nothing to do with database memory vs. other memory. > Both database and non-database routines return handles, which must be > locked into memory in order to reference the memory within them. The > difference between database and non-database memory is that database > memory is write-protected, so that you need to use special means (the > DmSet and DmWrite calls) to write to database memory. > > > -- > For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
