ADT/ODE: End Statement in Run-Time Application Causes Error (165824)
The information in this article applies to:
- Microsoft Access Developer's Toolkit 7.0
- Microsoft Office 97 Developer Edition
This article was previously published under Q165824 Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
If you use the End statement in Visual Basic for Applications code in a
run-time application, when the statement is executed, you may receive the
following error message and then the application quits:
Execution of this application has stopped due to a run-time error.
The application cannot continue and will be shut down.
Note that this does not happen in the retail version of Microsoft Access.
CAUSE
The End statement causes a UserReset error in Microsoft Access, which is
treated as a run-time error. Run-time errors in a run-time application
cause the application to quit. Note that this happens even if your
application contains error handling procedures.
RESOLUTION
Rewrite your code so it does not use the End statement. If it is
appropriate, you can use the Exit Sub or Exit Function statement to exit
the procedure. Note, however, that the Exit statement only exits the
currently running procedure. If you are running a nested procedure, the
main procedure continues to run after you issue the Exit statement, and you
must provide a mechanism to exit the main procedure as well.
REFERENCES
For more information about the End statement, search the Help Index for
"End statement."
For more information about converting macros to Visual Basic modules,
search the Help Index for "converting macros."
Modification Type: | Major | Last Reviewed: | 11/21/2003 |
---|
Keywords: | kbcode kberrmsg kbprb KB165824 |
---|
|