>I use the ON ERROR command in the beginning of my program to call my own errorhandler (a procedure).
>When an error occurs in my application my errorhandler shows a messagebox with some information about the error, but then my application just continues executing after the line of code wich caused the error. This of course generates new error messages because I have already started to close down my application in the errorhandler.
>I want to be able to stop the code from executing and close all open databases, tables and windows and release the application. How shall I do?


Also, consider specifically trapping other errors in your error handling routine, such as record lock failure... And do not forget about the error event in the form. Check out the TT example with VFP. They use an error event routine in one of the base classes and another error handler at the form level. htwh.