VBA Runs After Application.Quit
On Apr 26, 6:09*pm, Andy wrote:
Delete all instances of Excel before you start. *Use the Windows
Task manager to do so. (Again, I am assuming you are creating
these instances of Excel without making them visible).
Good luck.
thanks Andy! Turned out to be the ol' memory leak issue with using an
open workbook as a data source for a DAO object. I had been working
with some open data for testing and thought I'd made sure I'd changed
all those references in the "finished" product, but I'd missed one.
Works killer now, though! I got a charge out of the client saying
"This is fun!" when he was "driving" while I was demo'ing it for him,
since he was used to dry, static statistics and metrics displays.
|