Return to Question

Update Feb 2023

This solution is no longer maintained here or on GitHub, mainly because I do not need a timer solution anymore. As seen below, the only purpose of this approach was to get a reliable, crash-free call that can get Excel out of UDF mode - which I've eventually achieved by posting a WM_DESTROY message to a userform. See here. The below is now purely an exercise in how to work from a remote application instance and get somewhat reliable timer functionality without crashes.

Update Feb 2023

This solution is no longer maintained here or on GitHub, mainly because I do not need a timer solution anymore. As seen above, the only purpose of this approach was to get a reliable, crash-free call that can get Excel out of UDF mode - which I've eventually achieved by posting a WM_DESTROY message to a userform. See here. The above is now purely an exercise in how to work from a remote application instance and get somewhat reliable timer functionality without crashes.

Added second solution. See Update section below

Update

Added a second solution using only native calls (plus the Sleep API) at Excel-VBA-SafeTimers

The native solution works on both Windows and Mac - calls Application.Run via a 'callback' object. At the above repository there is a comparison table showing the differences between the native solution (solution #1) and the Win API solution (solution #2 - the one originally posted here).

Added second solution. See Update section below

Update

Added a second solution using only native calls (plus the Sleep API) at Excel-VBA-SafeTimers

The native solution works on both Windows and Mac - calls Application.Run via a 'callback' object. At the above repository there is a comparison table showing the differences between the native solution (solution #1) and the Win API solution (solution #2 - the one originally posted here).