Yes, when the QUIT command is issued. I never witnessed it, it occurs at runtime. I have an on Error procedure that logs errors and that is why I know it is happening. The app could have uncommitted changes pending when the user exits. Do I need to protect against that happening?


>Patrick,
>
>Does this error occur when you issue the QUIT command in the app? Does it only happen at runtime or in the development environment? Do you have any sort of error handling in place (ON ERROR or overridden Error() methods)?
>
>Do you have any views open with uncommitted changes pending at the time?
>
>>I wish I could but I can not trace it back to anything other than the QUIT command.