Re: Problem in MemoryMgr.c...when performing a FldDelete

[krollin]

> I think the problem is that you are making the field text pointers
> point to empty strings, rather than setting them to NULL.

What is your basis for this claim?  Why should NOT setting a text field to NULL
result in a "NULL handle" error message?

AFAIK, James' approach should be OK.  I'd be interested in knowing what he finds
out by using a debugger and generating a stackcrawl/backtrace of the functions
between the call to FldDelete and the function generating the error message.

> if(debugfldH){
>     FldSetTextHandle(debugfldP, NULL);
>     MemHandleUnlock(debugfldH);
> }

The disposition of the handle should be in question.  You might use
MemHandleFree if the block were allocated dynamically. You might DmReleaseRecord
if the handle came from a database record.  I'm not sure when one would ever
call MemHandleUnlock.

-- Keith



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/