I have created macros to download bills and statements from their websites. Part of the routine for each is to call other macros that check if the date the bill/statement appears on the websites hasn't occurred yet, or if the bill/statement has already been downloaded.
I accomplish this by having at the start of each bill/statement macro an action that sets the variable Calling_Macro to %ExecutingInstance%. Inside the macros that check the date and/or if it is already downloaded I have an action to Cancel a Specific Macro of the instance: %Variable%Calling_Macro% if the date isn't current yet or the bill/statement has already been downloaded.
That works great if I run the macros for each bill or statement one at a time. However, I have also created a master macro that calls each of the bill/statement macros in turn. (i.e. each bill/statement macro is now a nested/child macro of the master macro). The very first one it came to wasn't ready to run yet and I saw it got cancelled. However, that also cancelled the master macro. That doesn't seem like it should have happened as the action is called Cancel a Specific Macro. I purposely did not run Cancel All Macros inside my sub-macros. I know I could work around this by setting variable in my sub-macros and then check them in each bill/statement macro, and then run Cancel Just This Macro from the particular bill/statement, but this is not elegant and seems contrary to the whole purpose of Cancel a Specific Macro.
So, the bottom line is: 1) Why is Cancel a Specific Macro also cancelling the parent/master macro and 2) Is there a way to cancel just that child macro from inside the 3rd macro? (the 3rd macro being the ones that check the date and if it was already downloaded).
Thank you,