Auto Debugging/Stop with Access 2003?

[Yin99]

Any way to make Access stop (enter code debug) *anytime* it runs VBA
code? I have hundreds of modules with VB code, and I couldn't
possibly set a breakpoint at every entry point.


-Yin

 

[Corey-g via AccessMonster.com]

Yin,

I thought you could just hit <ctrl> Break(Pause) and that would open a dialog
window asking if you wanted to continue, end or debug...

HTH,

Corey

 

[Yin99]

Yin,

I thought you could just hit <ctrl> Break(Pause) and that would open a dialog
window asking if you wanted to continue, end or debug...

HTH,

Corey

My main purpose is for reverse engineering the access database
application. Thus, whenever a form button is clicked (any event
trigger), I see what code its stopping in, and can step through code
back to form. Ideally, I could set Access into a "Global VBA Code
Debug Mode" so it just stops anytime entering code, but its looking
like thats not possible.

 

[RD]

My main purpose is for reverse engineering the access database
application. Thus, whenever a form button is clicked (any event
trigger), I see what code its stopping in, and can step through code
back to form. Ideally, I could set Access into a "Global VBA Code
Debug Mode" so it just stops anytime entering code, but its looking
like thats not possible.

AFAIK, that is correct, there is no way to just make it break for no reason.

If you're reverse engineering then the way to go *IS* to put a breakpoint on the
event handler for a control. Then you step through everything that happens
after that. I was once hired to document an old Access application that had
been developed by a contractor a few years before. One by one I put breakpoints
behind event handlers and finally figured out what the heck that thing was
doing.

Good luck.
RD