Adrian, >I didn't try in C yet. But, I am sure you will.
This has been in C... >Here it is the sequence: Interesting this ever worked for you consistently. You aren't doing the MemMove() until after you have unlocked the handle from the original resource. I guess there is nothing between it and the MemMove which is necessitating the movement of existing handles in the storage heap. But as a general rule, I would not recommend the sequence below. I would put the unlock and release of the resource *after* the MemMove() instead. >MemHandleLock >MemPtr = SysTrapFunc(33,1,MemHandle) >MemHandleUnlock >DmReleaseResource >... Now, MemMove() part... >MemPtrNew >MemMove etc. >This complete sequence would allow you make some tests with your 3k bitmaps. Wel, other than the timing of the MemMove, that is essentially what I am doing, except I don't write it back to the database. And I find it hard to believe that your timing on the MemMove vs mine is what makes yours work... >Probably, there is something more we are not seeing... I think I'll chalk this up to the tempermental handling of bitmaps Robert describes. I'll use the method Robert describes. It at least is working consistently for me. Doug -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
