General information
Category:
Visual FoxPro and .NET
To which I would add: an error thrown when you try to send an email. Right before that if... call, try issuing:
on error quit
Hank
>>Hi
>>
>>I have a program which runs in a Windows 10 machine with the following code at the end of the program. The program runs every hour and usually takes about 20 minutes
>>
>>About twice a day it hangs up with a message "cannot quit visual Foxpro" Any ideas why?
>
>The possible reasons, off the top of my head:
>1) some code still running (the most probable cause)
>2) dirty buffer with unwritten changes (though that would give you a different error most of the time, unless the attempts to write involve running code - in viewadapter, RI database code and such)
>3) dangling reference to an object which just won't get killed (this usually happens silently and in development, haven't seen much of that in runtime).
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only