MS Access Runtime closes database when there is a mirror error. How to ignore?

[minimen456]

There is a MS Access Database. Sometimes there are pop ups errors: "The value you entered isn't valied for this field" and then a Macro error. But that's OK, I just click "Stop All Macros" and give it another try.

But with MS Access 2016 Runtime it's different. The database just closes. How to make it behave the same way as full MS Access 2016? I don't want to database being closed when there is a minor error.

 

[arnelgp]

it's runtime so you have no control of it.
make sure that all your code is working before
converting it to runtime.

 

[Minty]

You have to handle all errors to avoid a runtime database closing.
So in your case above you need to validate the entries before saving the record to avoid the error being raised.
Use the forms before update event, or use a combo box to restrict the end users entries. There is an excellent video here:

Bad Data is Bad for Business #1 and #2

I just added #2 --- that link is further down. It is much shorter than #1. I also added a copy of the database I used for the video. Enjoy:) I created a database to help people to understand how and why to use the Form's BeforeUpdate event to validate data. @Uncle Gizmo and I made a...

www.access-programmers.co.uk

 

[gemma-the-husky]

There is a MS Access Database. Sometimes there are pop ups errors: "The value you entered isn't valied for this field" and then a Macro error. But that's OK, I just click "Stop All Macros" and give it another try.

Your process is still failing when this happens. When you stop all macros, you might be introducing other errors. It depends what happened before, and what was supposed to happen after the failed step. With runtime any error just crashes your programme. That's the difference.

As others have said, you need to include error handling, and data validation so that you can't get any errors of this nature.