Automation stays in memory!

Automation stays in memory!

I have a COM server used by vba (msaccess) it appears that teh dang thing STAYS in memory after the vba clint is done ( and "removes the reference" successfully) and even if I copy a new DLL AND register it again while access is open.

The only way to get the new DLL to become effective is to completely shut access down and back on, again.

Is there a way for the server to unload itself (or from within vba, or some other place to free unused libraries??) without shutting access down.

Any hints will be VERY much helpful.

TimH

4 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.

Have the client call the WIN API routine CoFreeUnusedLibraries

Thanks,
The registry solution works but it really should be reserved for "low memory" systems since it totally disables chaching which under other cirsumstances may cause big slow downs.

Tim

Laisser un commentaire

Veuillez ouvrir une session pour ajouter un commentaire. Pas encore membre ? Rejoignez-nous dès aujourd’hui