Assert vs Stop

[foxguy]

Is there any advantage to one of these over the other? gbDevelopment will only be True on my computer. It will never be true on a distributed file. And the distributed file will not be compiled into an executable. It won't even be password protected.

Please Login or Register  to view this content.

[MarvinP]

My question would be the stack and cleaning it off. Also, it might be better to branch down to an error routine to see why you got there.

Read: http://www.fmsinc.com/tpapers/vbacode/Debug.asp section Writing Code for Debugging.

[Leith Ross]

Hello foxguy,

As far as VBA is concerned there is no difference between Stop and Debug.Assert in the IDE. When Stop is compiled into an executable program, it behaves like the End statement. It will then close any open files and clear all variables.

Personally, I like the Stop statement since it is clear what the code is doing. Debug.Assert breaks the code when the condition is False. Some carry over from the days of yore in "C".

[shg]

Leith, I don't think Stop behaves like End at all. Specificably, it does not clear variables, it just halts code excution.

[Leith Ross]

Hello shg,

It will if compiled in an executable (.exe). However, that really isn't an issue with VBA.

See this article: http://msdn.microsoft.com/en-us/libr...8VS.60%29.aspx

Note: This applies to VS 6.0 and VB.net

Form the VBA help files:

The Stop statement suspends execution, but unlike End, it doesn't close any files or clear variables, unless it is in a compiled executable (.exe) file.