Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
thanks! that's exactly what I was looking for!
Phil "Jim Cone" wrote in message ... Under Tools | Options | General (tab) in the VBE, change Break on unhandled errors to Break on all errors. -- Jim Cone Portland, Oregon USA http://www.mediafire.com/PrimitiveSoftware (Formats & Styles: lists/removes unused styles & number formats - in the free folder) "Phil B" <phil.remove.brady@hotmail dot co dot united kingdom wrote in message ... 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 |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Excel 2003 + hungapp errors | Excel Discussion (Misc queries) | |||
errors in Excel 2003 | Excel Programming | |||
errors in Excel 2003 | Excel Discussion (Misc queries) | |||
excel 2003: Module errors | Excel Programming | |||
Excel 2003 Updates, and Errors | Setting up and Configuration of Excel |