I have an application that i've created in Access 2003. Within this
application I import a file via a cmd button using the windows common
dialog box. I've used some error trapping in those functions that have
the transferspreads heet command (within the import code). It's a
simple "On error Goto Trap1" then I trap the error store it in a table
and just "Resume Next" which is the end of the function.
What has happened is that now in other procedures if I have a runtime
error the error won't display it just quits.
I realize that for some reason the error handler in the other module is
somehow diverting the other procedures errors, how do I get around this
to ensure I can see what my errors are?
application I import a file via a cmd button using the windows common
dialog box. I've used some error trapping in those functions that have
the transferspreads heet command (within the import code). It's a
simple "On error Goto Trap1" then I trap the error store it in a table
and just "Resume Next" which is the end of the function.
What has happened is that now in other procedures if I have a runtime
error the error won't display it just quits.
I realize that for some reason the error handler in the other module is
somehow diverting the other procedures errors, how do I get around this
to ensure I can see what my errors are?