> Memory allocated by DmNewHandle is a bit risky because such memory
> isn't associated with a database. It is orhpaned memory. This means
> the user can't delete it. Orhpaned memory is cleaned up when Palm OS
> is reset ...
Is there any way to test for orphaned data memory? Perhaps a count
during startapp and stopapp to debug any potential leaks?
DmNewHandle was suggested as a place to store a temporary array that
is too big for the dynamic heap. I suppose the alternative is to
create and destroy temporary databases. If so, is there a way to get
a unique temporary db name?
Thanks,
- Ron Nicholson
