devxlogo

Tie a Message Box to Debug.Assert for Advanced Debugging

Tie a Message Box to Debug.Assert for Advanced Debugging

Placing a message box in an error trap can provide useful debugging information, but it doesn’t allow you to return to the subroutine or function to poke around and further debug the code. This version of a message box expedites design-time debugging by breaking execution if the developer presses OK:

 Private Function MyDebugMsg(ByVal aMessage _	As String) As Boolean	' This function is used for expediting 	' development	If MsgBox(aMessage, vbOKCancel, _		"OK puts you into the Error Trap") = vbOK Then		MyDebugMsg = False	Else		MyDebugMsg = True	End IfEnd Function' Sample subPublic Sub SetColor()On Error GoTo SetColorError' body of the subroutine would go here,' force an error to demonstrateError 5SetColorErrorExit:	Exit SubSetColorError:	' In an error trap place this line in addition to any	' other error handling code	Debug.Assert MyDebugMsg(Err.Description & " in SetColor")	'other error handling code	Resume SetColorErrorExitEnd Sub
See also  5 Tips for Working With an Onsite Interpreter
devxblackblue

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist