How to use "Step into"

  • Thread starter Thread starter Robin Chapple
  • Start date Start date
R

Robin Chapple

I have some code that needs debugging and the use of the "Step into"
feature seems to be the way to debug it.

If I use " Debug > Step into " I can see nothing added to my code.

If I enter a single breakpoint that is indicated by a brown highlight.

How should I use "Step Into" ?

Thanks,

Robin Chapple
 
Robin Chapple said:
I have some code that needs debugging and the use of the "Step into"
feature seems to be the way to debug it.

If I use " Debug > Step into " I can see nothing added to my code.

If I enter a single breakpoint that is indicated by a brown highlight.

How should I use "Step Into" ?

Thanks,

Robin Chapple
Click to expand...

Step into doesn't change your code at all, it simply executes one line at a
time. When the code execution gets to the break point it will stop, yet all
variables will be retained. You can then use the F8 key to single step
through the code. At any point you can see the value of variables by
hovering the mouse over them or you can print values in the immediate
window. The difference between "Step into" and "Step over" is that with the
latter, the code window will remain in the current procedure while executing
the code for functions that you have "Stepped over". With step into, it
will go line by line through every procedure.

HTH
 
Just to be sure that I understand.

i) I insert a breakpoint;
ii) run the code;
iii) and use F8 to execute each command.

Is that correct?

Thanks,

Robin Chapple
 
Robin Chapple > said:
Just to be sure that I understand.

i) I insert a breakpoint;
ii) run the code;
iii) and use F8 to execute each command.

Is that correct?
Click to expand...

Yes, correct. Single stepping code is an important technique for debugging.

Regards,
Randy
 
Back
Top