QUIT command Doesn't Kill Process

[Steve Meyerson]

VFP9 SP2

I'm not sure whether this is caused by VFP, XP or me. I've not had
this problem before (that I'm aware of, anyway), so I suspect it's
something I forgot or did differently.

My executable runs fine and the process (Payroll.exe) appears in the
task manager list of processes, which is expected. After the exe is
terminated, however, (either with or without the QUIT command in the
Destroy method), the process stays in the list. I've tried it on 3 XP
computers and get 2 different behaviors.

Computer 1&2: Cannot restart the exe. Error msg says process is
already running.( VFP is not installed.)

Computer 3: Restarts ok, but a new process with same name is added to
the list on each restart. I presume it would eventually run out of
memory. (VFP is installed).

I've actually worked around the problem by killing the process using a
program I installed from the internet. The last line of the my
Destroy method:

RUN /N C:\Program Files\KillProcess\KillProcess.exe Payroll.exe

But isn't there something I could do in VFP to kill the process when
exiting the executable? It restarts ok when I run the program from
Main prg.

Thanks for any help.

Steve

[Dan Freeman]

Post by Steve Meyerson
VFP9 SP2
I'm not sure whether this is caused by VFP, XP or me. I've not had
this problem before (that I'm aware of, anyway), so I suspect it's
something I forgot or did differently.
My executable runs fine and the process (Payroll.exe) appears in the
task manager list of processes, which is expected. After the exe is
terminated, however, (either with or without the QUIT command in the
Destroy method), the process stays in the list. I've tried it on 3 XP
computers and get 2 different behaviors.
Computer 1&2: Cannot restart the exe. Error msg says process is
already running.( VFP is not installed.)
Computer 3: Restarts ok, but a new process with same name is added to
the list on each restart. I presume it would eventually run out of
memory. (VFP is installed).
I've actually worked around the problem by killing the process using a
program I installed from the internet. The last line of the my
RUN /N C:\Program Files\KillProcess\KillProcess.exe Payroll.exe
But isn't there something I could do in VFP to kill the process when
exiting the executable? It restarts ok when I run the program from
Main prg.
Thanks for any help.
Steve

Your program is not properly ending.

QUIT is never necessary in a runtime app. When your user chooses to
exit you should issue CLEAR EVENTS and let the application's cleanup
code execute before exiting.

If you use a READ EVENTS (you should) and do not issue CLEAR EVENTS,
QUIT will be ineffective.

Dan

[Steve Meyerson]

Post by Dan Freeman

Post by Steve Meyerson
VFP9 SP2
I'm not sure whether this is caused by VFP, XP or me. I've not had
this problem before (that I'm aware of, anyway), so I suspect it's
something I forgot or did differently.
My executable runs fine and the process (Payroll.exe) appears in the
task manager list of processes, which is expected. After the exe is
terminated, however, (either with or without the QUIT command in the
Destroy method), the process stays in the list. I've tried it on 3 XP
computers and get 2 different behaviors.
Computer 1&2: Cannot restart the exe. Error msg says process is
already running.( VFP is not installed.)
Computer 3: Restarts ok, but a new process with same name is added to
the list on each restart. I presume it would eventually run out of
memory. (VFP is installed).
I've actually worked around the problem by killing the process using a
program I installed from the internet. The last line of the my
RUN /N C:\Program Files\KillProcess\KillProcess.exe Payroll.exe
But isn't there something I could do in VFP to kill the process when
exiting the executable? It restarts ok when I run the program from
Main prg.
Thanks for any help.
Steve

Your program is not properly ending.
QUIT is never necessary in a runtime app. When your user chooses to
exit you should issue CLEAR EVENTS and let the application's cleanup
code execute before exiting.
If you use a READ EVENTS (you should) and do not issue CLEAR EVENTS,
QUIT will be ineffective.
Dan

Hi Dan,
I put the CLEAR EVENTS as the last line in Destroy(), removed the QUIT
and guess what? It worked. THANK YOU!

p.s. Now I have to wonder why my clients' machines haven't crashed (or
have they?? :)

Steve