Weird "Break On Error" need?

From: U-CDK_CHARLES\\Charles (_at_aol.com)
Date: 12/21/04 

Date: Tue, 21 Dec 2004 20:46:59 GMT

List:

I need to do something that the error trapping mechanism doesn't seem to
support.

I have some functions: File access, "exist" methods on collection
objects . .that rely on the vb error mechanism to work.

I'm currently debugging a function.

"Break on All Errors" and "Break in Class Module" of course don't work,
as I have to deal with dozens of spurrious errors.

"Break on Unhandled Errors" folds the error up to an unrelated function
in the call tree.

How do I disable error handling ONLY at particular times in the affected
function.

On Error Goto 0 just seems to propagate the error upwards.

Suggestions?

Thanks