Negative, it's not locked, in fact nothing is locked when the StrCopy is passed.
Sample App CW just wrote to memory location 0x001327C0 which is in the storage heap. In order to protect the integrity of the user's data, such direct access is not allowed. Instead, applications should use speceial Palm OS functions for this purpose. I'm not sure how or why the pointer structure to UnpackedRecord is in the storage heap, it shouldn't be there at all from I know of it. I guess I was hoping the answer was as simple as reallocating the data structure elsewhere, although I'm also not quite sure how that works. How it works is the packed data takes a concatenated, delimited key from the database record. It's just one really long key with all of the fields delimited by '\30'. I have made a function that correctly extracts the fields from the record. The UnpackedRecord has absolutely no connection with the database. How it works is I make a MemHandle, the data goes into a PackedRecord structure with one field, ->key. Then from there I take the first field from the ->key and put it into TempString. So TempString will hold the primary key for the record, say, '3249238', now this is then copied to invidual fields in the UnpackedRecord structure, and this is where the error arises. I unlock the MemHandle, recH before any of this takes place, although I have also tried it while it is locked, and the error remains the same, so that can't be an issue, can it? , Jamie -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
