Robert said all you need to know. I'll just add some trivia... In the old days, there were multiple storage heaps. When you called DmResizeRecord, it would try to resize the record's handle in the current storage heap, first by grabbing more space where the chunk currently lives, and if that wasn't possible, then by allocating a new chunk in the same heap. If both of these failed, it would try to allocate a new handle in another storage heap. This is why DmResizeRecord returns a handle, and why you should use the returned handle rather than continuing to use the original handle.
Any remotely modern version of Palm OS has a single storage heap on card zero. Devices with Springboard modules may have an additional storage heap on card one, but DmResizeRecord won't move records between cards. (In this case, it would obviously be inappropriate.) So in practice, you probably don't have to worry about DmResizeRecord returning a different handle. That said, I'd still use the returned value; it doesn't hurt. -- Danny @ PalmSource -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
