I'm developing some vba macros under excel 2003 and am (naturally) getting
errors.
Compile time errors highlight the offending line, but seemingly not run time
errors.

All I'm getting is a helpful message eg 'Invalid procedure call or argument'
but no clue as to which line of code is giving this.
Isn't it possible to get the environment to highlight the offending source
line?
There must be a better way than a liberal sprinkling of print and msgbox
diagnostics.

regards
Phil B