application object variables best practices? - 08-01-2012 , 12:19 PM
I have a db that exports datasets to Excel many times in a typica use case, i.e. monthy reporting.
The report exports vary enought that I have not been able to build the export procedures into one generic one.
Currently I dim the Excel.Application object in each export and then quit:Set to nothing.
I wonder if I should use a module level variable for excel application? How do I close it and release memory when done using?
Any advice welcome.