Advice with using Application.OnTime function

[JeffGrant]

Hi All,

I use Application.OnTime quite a bit now and generally structure it such that the OnTime value is read from a column and then the row number is incremented to read the next time value. Generally works ok, but I have a situation where this increment method just wont be play nice.

So I am thinking about running the OnTime method through a loop and set up all of the OnTime calls in one go first thing in the morning.

This could easily be up to 100 OnTime calls during the week and up to 200 on a weekend.

Is there any reason that you folk know why this would not be advisable?

Thanks in advance

 

[Dan_W]

I suppose it depends on what you're actually doing, and how you code this mechanism, but I suspect this approach might cause you more headaches than it's worth.

If Excel is busy or you're using it in some way when the OnTime callback is executed, you'll get an error message that you'll need to deal with before you can continue using Excel. My suggestion would be to explore the possibility of using VBScript (which is a subset of VBA that you can run outside of Excel) that is scheduled to execute at certain times via TaskScheduler.

Again, it all depends on what you're doing and why, but my gut instinct is that there are more useful solutions than a blanket reliance on OnTime.