Got a break point question

[Brent E]

Good afternoon,

If I set a break point in my VBA module by clicking on the L. margin section
and a point gets inserted, I am curious if there's a way to make code resume
running after stopping at that break point? Or do u have to run the procedure
from beginning again? Is there a way to step thru many break points? Thanks.

Cordially,

 

[Dirk Goldgar]

Good afternoon,

If I set a break point in my VBA module by clicking on the L. margin
section and a point gets inserted, I am curious if there's a way to
make code resume running after stopping at that break point? Or do u
have to run the procedure from beginning again? Is there a way to
step thru many break points? Thanks.

When the code execution has halted at the breakpoint, you can resume
execution by pressing F5, or clicking the "Continue" button on the
toolbar, or clicking menu items Run -> Continue.

Did you try looking in the help file first? If you had typed "continue
execution" in the "search help" box, the first topic listed (in A2K2,
anyway) would have been "Continue Code Execution", which explains all
about it.

 

['69 Camaro]

Hi, Brent.

I am curious if there's a way to make code resume
running after stopping at that break point?

In the built-in toolbar, there is a green triangular "Run" button. Select
this button and the code will continue to execute up to the next breakpoint
or until if finishes. Alternatively, press <F5> or select the Run menu ->
Run Sub/UserForm.

You have several other options available for debugging. After the code
stops at the breakpoint, place the cursor two or three lines below the break
point, then open the Debug menu and select the "Run To Cursor" option.
Notice that code executes up to the line of code where you placed the cursor,
then it stops again, awaiting the next command.

You can also effectively skip lines of code within a procedure when
necessary by placing the cursor on a specific line of code while in break
mode, selecting the Debug menu again and then selecting the "Set Next
Statement." The yellow highlight (signifying the next line to be executed)
will jump to the line where your cursor is located, awaiting the next
command, such as "Run."

There's also Step Into, Step Over, and Step Out for debugging through
procedures. I suggest experimenting with these options to see what they do
so that the next time you have a problem to debug, the VB Editor can assist
you in finding the bug even faster.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. (Only "Answers" have green
check-marks.) Remember that the best answers are often given to those who
have a history of rewarding the contributors who have taken the time to
answer questions correctly.