break point on errors

[snerting]

Hi

I have certain access 2003 VBA applications where code errors tend to break at a much prior point in the "call stack" than the actual error. With long while loops etc, it is really painful to debug as stepping to the place where the actual code breaks takes lots of time. Not to mention cases where the code will only break the first time it is run, in which case I have to restart the application to reproduce the error.

Like it behaves now, I have to set new break points every so often and press F5 to see if the code made it that far and so on.

Any tips on what might be causing this?

Any help is highly appreciated.

 

[TheAceMan1]

How are ya snerting . . .

To a certain extent you can [blue]control when running code will break on error[/blue].

In the VBE editor select [blue]Tools[/blue] - [blue]Options...[/blue] - [blue]General Tab[/blue] - and select the help button. See the section for [blue]Error Trapping[/blue].

See Ya! . . . . . .

 

[snerting]

Thanks, I changed from

"Break on unhandled errors"

to

"Break on all errors"

And it seems to work like a charm .


Thanks TheAceMan1 !