Hi John,

I'm not *quite* sure that I understand the problem...

Since the 'AddressOf' operator is available in 2002, why are you adding the
requirement that you have a similar functionality that takes a string
instead?

But given that this is the requirement, I would still think that using late
bound calls either via Execl.Application.Run() or VBA.CallByName() should
also do the trick. I guess late-bound calls are a tad slow, but if this is a
callback, the slight loss of time should not matter. Admittedly it would be
nice to determine the AddressOf from the "name" only once, not each time the
timer fires (as would be implied by repeated calls by VBA.CallByName() or the
like), but I'm not sure that it's worth the effort here?

Using the proper 'AddressOf' operator itself, however, instead of a
home-brewed reflection-based function would seem to be much better though,
yeah? But I guess I don't quite know why you have this set of requirements.

An class interface-based callback would be another natural choice as well,
but, again, I don't know what your needs are.

Just some thoughts! But I don't know if any of this is actually helpful, my
guess is you are aware of all of these options...

-- Mike