I have a MS Access database and have "on error" routines for every VBA function, subroutine and event. Still, I get errors that pop up like "Invalid use of null" or "overflow error" that do not fire the "on error" logic. Why not?
I have a routine that runs monthly, importing Excel spreadsheets provided by banks and credit companies. Each record entails quite a bit of logic, so the routine is all VBA. Without the "on error" logic firing, ACCESS doesn't tell you where the error occurred, so debugging is difficult. There are too many lines of VBA and too many iterations of those lines of VBA to step-thru.