Hey guys, long time lurker- first post. I have a front end I developed that includes error handling in every method. When an error is raised it goes to a procedure that logs it, and tries to handle it if it's a known issue. I keep getting error 3043: "Your network access was interrupted. To continue, close the database, and the open it again." I'm quite certain this has to deal with not using the UNC path when linking my tables, and my mapped drives (I work for a large company that regularly performs maintenance on its servers). The simple fix is to change all of my linked table paths - WHICH I AM GOING TO DO.

My question is: Why doesn't this go to my error handling?

I get a "Microsoft Visual Basic" pop-up box with the error number, and the above statement with the options to end or debug. I can manually throw error 3043 and my code will catch it, but when it happens on its own I get the pop-up and no custom error handling. Any ideas why?

* Design should never say "Look at me". It should always say "Look at this". -- David Craib* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc

All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...(you are responsible for your choices and actions)

Thanks for the confirmation. That's kinda what I was expecting; which [censored], because before I came to that conclusion I developed this elegant af solution. I'll have to find somewhere else to use it.