M
Mauricio Villada
Hi,
This is an odd behavior I noticed in one of my client's machines:
He has fileA.xls and fileB.xls opened in Excel. Both files are based on the
same template so they have the same Macros (that in turn point to a COM
DLL).
In the VBA Editor I can see the macros associated to each one of the files.
When I close one of the files, Excel closes it but when I take a look in the
VBA Editor it turns out that Excel doesn't unload the associated macros
immediately. After a while it finally does it but in this small period of
time is causing some conflicts with the workbook that continues to be
opened.
Has anybody come accross this odd behavior?, how can I isolate one Excel
file from another (including isolating the macros and DLLs associated)?
Thanks,
MV
This is an odd behavior I noticed in one of my client's machines:
He has fileA.xls and fileB.xls opened in Excel. Both files are based on the
same template so they have the same Macros (that in turn point to a COM
DLL).
In the VBA Editor I can see the macros associated to each one of the files.
When I close one of the files, Excel closes it but when I take a look in the
VBA Editor it turns out that Excel doesn't unload the associated macros
immediately. After a while it finally does it but in this small period of
time is causing some conflicts with the workbook that continues to be
opened.
Has anybody come accross this odd behavior?, how can I isolate one Excel
file from another (including isolating the macros and DLLs associated)?
Thanks,
MV