So much great information in just 20 minutes. I'll definitely rewatch this a few times, but this will help me save so much time debugging. Thanks Paul!
Thanks for this video. For me it didn't contain much new stuff, but I recommend this video all the time to VBA beginners: friends, colleagues and on Stack Overflow.
This is great. I've also been exploring the usefulness of debug.assert to stop when a value doesn't match what's expected. Not sure if there's any advantage over a watch.
I didn't think I could get anything new from the video, but... this 'Add Watches & Break if True' is really cool tip. Thank You for that :) Maybe I have something for You - do You know that You can manually move the yellow line (break mode) some lines further or before? It helps me a lot in debugging.
Excel Macro Mastery...I need help! I have been running into a brick wall concerning PasteSpecial x1PasteValues error. How do I correct this error? If you've explained this specific example, please please point me to your video. Thanks!!
Do you have any examples where a function can be used in the "Break When Value Is True" Watch option is used? I'm trying to figure out where in my code a particular data connection is getting inadvertently moved/renamed which causes subsequent data refresh steps to fail. I created a function that should tell me if the Connection exists but adding it to the watch window [via something like ConnExists("Connection Name")] always shows "" and I wasn't sure if something like a function that returns a Boolean could be used in a "Break When Value Is True" watch option. 🤔
I don't think you can do that with a function. If possible you could return the function to a variable and put the watch on that. Another idea is to use the Debug.Assert line which will pause if the condition is false. See this video for more about Debug.Assert(ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-CT7XkPXKVFw.html)
Great intro. (In decades of using VBA, I'd never pondered what Set next statement even meant. Too soon old, too late smart.) Two comments: 1) the advantage of Run to cursor vs setting a breakpoint is you don't have to clear the breakpoint afterwards if you don't want to keep stopping there during this session. 2) I'm somewhat surprised you never mentioned the Immediate window. Some of the things you showed for watch are occasionally better suited to Immediate (i.e., ? x+7700). Also, Immediate allows you to modify variable values on-the-fly (i.e., loopcount=maxloopcount-1). Not to mention Debug.Print...
Thank you for this video. I've been missing a lot of things in debugging my vba. This is very helpful. Breaking in a loop is awesome. I have been struggling with that. Now I know how. Thanks again
I'm relatively new to vba and self taught, I often read that "call" is depreciated and "application.run" should be used instead? What are the advantages and disadvantages of each?
