Debugging a VBA following the code as it executes

I would suggest reading chapter 3 in the Learning MicroStation VBA book that discusses how to use the IDE (including loading and debugging)

This appears to deal with errors.  I am not getting an error just an undesired result.

It does not address watching the code execute line by line as I think to find the code that is providing the result is the only way to see what is actually happening.

What I want to do is execute the command, watch it go from one line of code to the next and not proceed until I send it to the next line.

I have tried using several of the commands under the Debug tab but they do not seem to accomplish this.

BTW Chapter 3 section in the edition I have refers to Chapter 9, what version are you using?

Brian MacCartney said:

What I want to do is to open the code, and then watch as line by line it executes

That's termed debugging.  Because of the similarity between MicroStation VBA and VBA on other platforms, such as Office, you can generally search all websites that deal with VBA for help and tips.  For example, here's an Excel website that discusses debugging.

• You can tell the code to stop at a breakpoint
• Continue step-by-step using key F8
• Hover the mouse over a variable to see its value

Hi Brian,

as Jon wrote, you have to set the breakpoint into VBA code and start macro. When VBA interpreter reaches the breakpoint, it stops and you can go through the code line by line.

Of course, it leads to a question where to place the breakpoint. You have to find, what method (sub in code) is called, when the macro is started. It should be clear from the used key-in, or maybe there is only one public subroutine in the macro. Without knowing the code, it's hard to defined it more exactly.

With regards,

  Jan

okay think I got that to work now just have to find the code that places the cell...seems to be caught in a loop using the F8 key tho...

Brian MacCartney said:

seems to be caught in a loop using the F8 key

If you're stuck in a loop that's nothing to do with the F8 key.

Brian MacCartney said:

just have to find the code that places the cell

Search the code (Ctrl-F) for one of the cell creation methods, probably CreateCellElement2 or CreateCellElement3.  Place a breakpoint on that line and run the code afresh.

The "loop" effect that you see might be the code's waiting for a user input (perhaps datapoint?) 

Tuan Le said:

The "loop" effect that you see might be the code's waiting for a user input (perhaps datapoint?) 

Even though the idea makes sense, such loop should never exist in MicroStation VBA code, because every interaction with mouse (data point, reset...) must be implemented using IPrimitiveCommandEvents and ILocateCommandevents objects.

Regards,

  Jan

Hi Brian,

Brian MacCartney said:

okay think I got that to work now just have to find the code that places the cell

It's great :-)

You can go through the code "from top to down", because from the code snippet you shared (and probable removed, because I do not see it now), the tool is called from VBA form, so you have to check what code is called by this button "Click" method.

To use opposite direction is also useful, and as Jon wrote, to search for CreateCellElement method helps.

Brian MacCartney said:

seems to be caught in a loop using the F8 key tho...

It's weird, because there is no reason why there should be any loop. The only loop can be scanning model content, using ElementScanCriteria. But it is rarely used when element is created (placed).

Regards,

  Jan

Hi Brian MacCartney,

You may find some of these topics to be helpful to make more progress quickly:

• Getting Started with VBA in Office
• Debug Microsoft VBA and Debug MicroStation VBA
• Search for Text in Code and STOP

HTH,
Bob