1. Ftr Memory IS in the db cache so your last question is meaningless
2. Allocations ARE NOT guaranteed to be at start of heap unless you ask for
it (hence FtrPtrNEw and MemPtr new are bad for long-term allocations)
3. The code I posted allocates a chink of that size as close to the end of
the heap as possible, marks it as used and locked, and returns a pointer, to
which you may write using DmWrite
Thia way your allocation does not fragment the heap as much
Best Regards,
Dmitry Grinberg
(847) 226 9295
On Tue, Sep 9, 2008 at 6:50 AM, Lionscribe <[EMAIL PROTECTED]> wrote:
> Dmitry,
> Can you explain the idea behind this to us simple souls.
> I imagine you are trying to imitate MemPtrNew (with allocation at bottom of
> heap) in the dbMemory,
> but please explain.
> Also, wouldn't it be better to use feature memory, so that we can close
> database?
> Lionscribe
>
> --
> For information on using the ACCESS Developer Forums, or to unsubscribe,
> please see http://www.access-company.com/developers/forums/
>
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
