VBA releases memory when it is appropriate. There are certainly bugs that
cause memory leaks, but I haven't heard of any associated with assigning
variables.

--
Regards,
Tom Ogilvy

"ct60" wrote in message
...
Hello again,

I have code which involves many objects that have references to each
other.

This causes large memory leaks since VBA is not able to deaalocate all
memory that has gone out of scope. So, I set all references, etc to
NOTHING
when the objects terminate. Problem is there is still a significant
memory
leak AND it is quite time consuming.

So does anyone know of a fast way to deallocate memory? The Unload
statement does not seemto help either.

What might be ideal is maybe a windows API function that deallocates
memory.
In theory we should be able to point to an address in memory and a size of
the object structure and free that memory. Does anyone have know the
details
of we can do something like that?

Any insights would be greatly appreciated.

Thanks,

Chris (ct60)