#EXCEL VBA DEBUG PRINT CODE#
You can click into the grey margin to set a breakpoint or click into a line of code and then select Debug | Toggle Breakpoint or use the F9 shortcut key. This is useful in long procedures where it would be tedious to step through every line of code before you get to the part that you are trying to debug. You can set a breakpoint in your code so that all code above it is executed normally but from your breakpoint onwards you can step through the code. To see what your code is actually doing, split your screen so that the VBE and Excel are both visible. Press F8 again and the next line of code will be executed and so on and so on. The first line of code will be highlighted in yellow and when you press F8 again, that line of code will be executed. To step through code you need to put your procedure into break mode: Click Debug | Step Into or use the F8 shortcut key. By stepping through code you are much more likely to identify and resolve any problems. This might be useful if your procedure produces unexpected results or an error. When you step through code you are executing one line of code at a time. Run-time error are covered in more depth in the tutorial on Error Trapping and Handling. For this reason you will need to build error handling code into your procedures in expectation of any of these problems. Some run-time errors occur not because of errors in your code necessarily but because the procedure encounters unexpected things in your data like missing workbooks, worksheets or values, or unexpected data types. Use the VBE’s Continue button to resume running the code or use the F5 keyboard shortcut. This will allow you to fix your code and then resume code execution from the break point.
To fix the error, you need to click on the Debug button on the run-time error dialog box. This is the run-time error displayed for this code. Lines of code above the break point have been successfully executed. The yellow arrow and yellow highlighting indicate the position at which the code stopped – the break point. Run-time errors put your procedure into break mode: break mode temporarily stops the code running until you fix the problem and resume execution. The code below attempts to select a sheet that is not available and therefore produces a run-time error. Run-time errors do not appear in red like a syntax error, nor do they occur when you compile a procedure (compile without running), but they do occur when you attempt to run a procedure. For example the misspelling or vbRed in the code below is only picked up as a compile error if Option Explicit is used. Using Option ExplicitĪlways use Option Explicit so any errors you make referring to variable names or other misspellings are picked up when you compile your code. If you just compile the procedure rather than compile and run, the code will not enter break mode. Now you can fix the spelling error, Reset the procedure with VBE’s Reset button as shown below and attempt to run the code again. You can see below that the first line of code is highlighted in yellow with a yellow arrow in the margin – this is the breakpoint (meaning the code couldn’t execute beyond this point) and the offending keyword is highlighted in blue. When you attempt to run the procedure you get this error message… In the example below, the Worksheets object name is spelt incorrectly. Code will always compile before it runs but you can compile without running it by clicking Debug |Compile VBA Project.Ĭompile errors are not shown in red, but you do get an error message when you compile the procedure. Syntax errors will still be displayed in red when you untick this option – so you will still be able to spot them!Ĭompile errors only become apparent when you compile your code.
You may want to turn Syntax error warnings off in Tools | Options |. For the second error it’s pretty useful for the first, not so useful. … or leaving out brackets where they are needed.įor both of the above syntax errors you get the same Compile error message. Syntax errors occur when you make a grammatical error in your code like leaving out speech marks when referring to a range… If you have a syntax error the offending code will be displayed in red and a Compile error warning will be displayed. Syntax errors occur as you are writing your code.
0 kommentar(er)
