Home/ Questions/Q 6903881
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T07:58:50+00:00

In Excel VBA, is it good practice to leave Debug.Print instructions in code that

  • 0

In Excel VBA, is it good practice to leave Debug.Print instructions in code that goes in “production” ? That is quite useful to debug the sheets realtime at the user’s machine when something goes wrong. Does it affect performance when Visual Studio is closed ? If not, what would you advise ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Debug.Print instruction DO have a small performance cost. So I would avoid them in loops that are executed a zillion times. Except for those cases, I think it’s ok to keep them.
    You could also use conditional compilation directives (#if) in combination with a compiler constant (#const) to enable/disable them globally without performance impact.

    #CONST developMode = True

sub Xyz
  #If developMode Then
    Debug.Print "something"
  #End If
End Sub
    • 0