VBA: Stop vs Debug.Assert?

[JenniferMurphy]

What's the difference between Stop and Debug.Assert in VBA code?

Thanks

 

[Norie]

Debug.Assert conditionally suspends code execution, Stop suspends code execution.

 

[JenniferMurphy]

Debug.Assert conditionally suspends code execution, Stop suspends code execution.

According to

https://www.oreilly.com/library/view/vb-vba/1565923588/1565923588_ch07-470-fm2xml.html

the "method" isn't supported in VBA. Does this mean that it is not conditional and, therefore, identical to Stop?

 

[Norie]

No it means you can't use Debug.Assert in VBA.

 

[JenniferMurphy]

No it means you can't use Debug.Assert in VBA.

Well, uh, er, ah, ummmmm... My question was about VBA, both in the title and the text. ???

 

[Norie]

There is no Assert method for the Debug object in VBA.

the Debug object in the VBA development environment doesn't support the Assert method.

 

[JenniferMurphy]

There is no Assert method for the Debug object in VBA.

Yes, so you said. My question now is why you didn't say that in your first response since I was specifically asking about VBA, not VB. Your answer, that "Debug.Assert conditionally suspends code execution," only applies to VB, not VBA. It would have been more helpful if you had said then that Debug.Assert is not supported in VBA.

 

[Norie]

Jennifer

To be honest I think I might be as confused as you are, and it was pretty early in the morning when I first posted.

Also, in post #3 I was referring to what was written in the article you linked too.


Anyway, Debug.Assert does appear to be available in VBA, here's a small example.

Dim I As Long

    For I = 1 To 10
        Debug.Print I <> 5
        Debug.Assert I <> 5
    Next I

When you run the above code execution will be suspended when I = 5, i.e. I<>5 returns False.

 

[Mousehunter]

YES! There is a Debug.Assert and it is used to stop the code execution when the condition ceases being true so it is a little bit counter-intuitive.

I prefer to set a watch and break when a condition is true. It is much easier to do so and during debugging I need to be focused on solving the problem, rather than being distracted by checking if my condition should be set this way or the other way round.

PS: Debug.Assert is much less popular than the Debug.Print which is practically in every book I have ever read. I only learned about Debug.Assert a couple of months ago...