Debug.Print strSQL


Is it advisable to have this code run all the time or is it only used when trying to fix an error?
I ask because there is quite a lot of accumulation of text in the immediate window and not sure if that is wasting memory.

thank you
pdvsaProject financeAsked:
Who is Participating?
Dale FyeCommented:
I usually either remark those lines out or delete them prior to publishing an application.

You can remark them out by simply doing a search on "Debug.Print" and replace with "'Debug.Print"
NorieVBA ExpertCommented:
Once you've got the code right then you don't really need it.

It's not doing any harm though.

Unless you need to use the Immediate window while debugging another part of the code, then things could get confusing.

pdvsaProject financeAuthor Commented:
ahhhh.  I see.   I will do that.  I believe I will use the Find and Replace Add In for this.  

thank you
pdvsaProject financeAuthor Commented:
Thank you.  Inmorie... fyed answered just a tad bit before.... thank you though.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.