Read our blogs, tips and tutorials
Try our exercises or test your skills
Watch our tutorial videos or shorts
Take a self-paced course
Read our recent newsletters
License our courseware
Book expert consultancy
Buy our publications
Get help in using our site
475 attributed reviews in the last 3 years
Refreshingly small course sizes
Outstandingly good courseware
Whizzy online classrooms
Wise Owl trainers only (no freelancers)
Almost no cancellations
We have genuine integrity
We invoice after training
Review 30+ years of Wise Owl
View our top 100 clients
Search our website
We also send out useful tips in a monthly email newsletter ...
When something goes wrong in a VBA class module, the default debugging settings aren't always very helpful.
Something has gone wrong in the Query class module. Surely clicking Debug will take me to the problem line?
By default, clicking Debug on the dialog box shown above only highlights the line of code in the procedure which calls the class module.
All this tells me is that there's a problem somewhere in the GetResults method of the class.
To get the VB Editor to take you into the class module when you click Debug, from the menu choose Tools | Options. On the dialog box which appears, select the General tab, choose to Break in Class Module then click OK.
Choose this option to change what the Debug button does.
The next time a run-time error occurs when using a class module, you can click the Debug button as normal:
The button looks the same...
This time, I'm taken into the class module and see which part of the offending method is going wrong:
Now I can see exactly which part of the GetResults method is causing the problem.
You can learn more about this topic on the following Wise Owl courses:
Kingsmoor House
Railway Street
GLOSSOP
SK13 2AA
Landmark Offices
99 Bishopsgate
LONDON
EC2M 3XD
Holiday Inn
25 Aytoun Street
MANCHESTER
M1 3AE
© Wise Owl Business Solutions Ltd 2025. All Rights Reserved.