snerting
Programmer
- Oct 20, 2005
- 52
Hi
I'm experiencing in some access VBA applications that if the code breaks, the break point set when I hit 'debug' is set a lot earlier in the call-stack than the line that actually broke. This makes it a pain to debug as I will have to step manually until the code breaks again. This is very time consuming. Any ideas of why access/vba doesn't set breakpoint at the line that actually causes the crash?
I'm experiencing in some access VBA applications that if the code breaks, the break point set when I hit 'debug' is set a lot earlier in the call-stack than the line that actually broke. This makes it a pain to debug as I will have to step manually until the code breaks again. This is very time consuming. Any ideas of why access/vba doesn't set breakpoint at the line that actually causes the crash?