Publishing database- Shut down run-time errors

[Ashe]

I'm handing my database off to a client who doesn't want to split it, but also doesn't want to see any potential VBA Run-time errors. I compiled the code and digitally signed the database.

Is there a way to shut down the VBA run-time errors to a generic "error" message, or no error message at all? We don't want any users to have the option of ever pressing "debug" and getting into the code.

[Ashe]

Could I use a module to set all warnings to off?

[Toyman]

Could I use a module to set all warnings to off?

The way I go around the error message is to put the followingat the beginning of each set of codes: "On Error Resume Next" or "On Error Goto ExitCode". "ExitCode" is a marker I set in the code right next to Exit Sub. This way, when an error is detected the code simply resumes or goes to the "ExitCode" marker which will end the code without an error message

[Ashe]

Do you do this for each sub? I have hundreds of sub code sets and probably 50 forms and reports with code behind them. I wonder if there's a way to globally define this...

[Toyman]

Could I use a module to set all warnings to off?

Do you do this for each sub? I have hundreds of sub code sets and probably 50 forms and reports with code behind them. I wonder if there's a way to globally define this...

Yes, you should always create an error trap for each one of your subs. Instead of having the error initiate an exit sub, you can create an error message. On the other hand, if all you want if not allow your users to be able to debug, then you can create a .mde or .accde depending on the version of access you are using and distribute that. In a .mde or .accde, all the user will get is an error message, and the only option is to click ok and the code exits.

In the years I have worked with access, I have learned to distribute .mde or .accde version of the db and never the .mdb or .accdb. In the .mde or .accde format, all the codes and form designs are locked. Your user cannot get to the design.