I have a macro which runs continuously for a customer. Basically, Macro1 runs early morning, checks for a database condition, an email inbox, and based on the results of these checks, calls Macro2 and Macro3 with the Macro> command. The "parent" macro runs all day. It waits a few seconds and loops back to a label. I have noticed (as has my customer) that there are times the macro shows to be running, but if you stop/start the macro, then it will "catch up" on the database activity and emails. It obviously wasn't running then when it appeared to be running.
Is there some limit to the length of time a Macro can run? Could there be some "memory leak" on this machine?
I have thought of writing a macro to stop/start the 'parent' macro, but it seems I should be able to run the program as is.
SkunkWorks
