Hi,
We have several DBs that contain global variables which are set either upon opening or during some other function.
However, when the DB experiences a runtime error, the code window pops open with a window asking to End or Debug.
In either case, the outcome is that all the global variables are reset to empty. So if the user selected the End button and tried to continue on in the DB, this would often create incomplete records, since some of the info is supplied by the global variables. And as a result, those records are not accessible because of the missing data.
We've tried instructing the users to select the End button, but then exit from the DB and then reopen it so that the globals are re-established. Either because of personnel turnover or ignorance, the user will try to continue using the DB after selecting the End button.
Is there a way to 'globally' capture any runtime error and cause the DB to close, without having to code every subroutine in the code window for that occurrence?
Thanks,
Vic
We have several DBs that contain global variables which are set either upon opening or during some other function.
However, when the DB experiences a runtime error, the code window pops open with a window asking to End or Debug.
In either case, the outcome is that all the global variables are reset to empty. So if the user selected the End button and tried to continue on in the DB, this would often create incomplete records, since some of the info is supplied by the global variables. And as a result, those records are not accessible because of the missing data.
We've tried instructing the users to select the End button, but then exit from the DB and then reopen it so that the globals are re-established. Either because of personnel turnover or ignorance, the user will try to continue using the DB after selecting the End button.
Is there a way to 'globally' capture any runtime error and cause the DB to close, without having to code every subroutine in the code window for that occurrence?
Thanks,
Vic