A breakpoint allows you to run your code and have it stop at a specific point before its natural end
When a breakpoint is encountered the application will enter break mode.
When a line contains a break point it is displayed in a different colour (red by default).
After a break point is encountered you can resume normal code execution by pressing F5 or (debug > Run).
You can enter more than one breakpoint into a procedure or function.

Inserting Breakpoints

There are several ways you can enter a break point once your cursor is on that line:
(Debug > Toggle Breakpoint)
(F9) - Toggles between inserting and removing a breakpoint
A red dot will appear in the margin infront of that line to indicate that a break point has been inserted.
You cannot place break points on blank lines, comments or variable declarations.
SS - screen shots of red break

Once a breakpoint has been added the line will be highlighted in red (or brown).

SS dialog that appears.

Removing Breakpoints

You can remove a breakpoint in exactly the same way.
(Ctrl + Shift + F9) - remove all breakpoints
(F9) - Toggles between inserting and removing a breakpoint
Breakpoints will be automatically removed when you close the Visual Basic Editor.

Using Stop

Since breakpoints are not saved within a file the stop command allows the creation of a breakpoint that can actually be saved.
This only works if the project is viewable.
This command is ignored if the project if password protected.

Placing a stop in your program places a semi-permanent" breakpoint so the debugger will be activated when the stop is executed.

Conditional Breakpoint



Breakpoints are not saved with a project when the project is closed.

© 2017 Better Solutions Limited. All Rights Reserved. © 2017 Better Solutions Limited