>>>I don't do much VFP work anymore, but for the past few days I've been working on a VFP/SQL Server application that involves a lot of Excel automation.
>>>Several times I got messages saying the computer is running low on memory (I have 16GB and tons of disk space with Win 10) and several times I had to reboot because everything was running slowly.
>>>I don't have these issues when doing .NET or PHP work.
>>>It might have nothing to do with VFP, but are they any known issues?
>>
>>embolded part - if interpreted meticously - says even after killing vfp tasks vial kill or task manager machine was unresponsive ?
>>Correct or were you just impatient and did not want to wait for task manager to pop up iwhen running with brakes on?
>
>As usual Herr TG is meticulous.

Only trying in thinking - gave up on the physical area around the keyboard.
Also keeping snake nests around routers, switches, hubs and power strips

Still, there is reason for this question: most of the times all resources gobbled up by faulty vfp programs (fragmented + overblown memory through faulty memory releases/cleanup, which can happen in activeX as well) will be released when the vfp process is killed.

If the machine is still slow with the vfp process gone, there might be residual activeX in own processes around, but that is quite rare IMO. More often some setting in Win was somehow reset (one example was DMA access reset to PIO), which cleared automagically often via reset.

So killing the process is a diagnostic step as well ;-))

>DO WHILE infinity
>   Get good response.
>   Become slow.
>   kill vfp process
>   if got good response
>      loop && and start thinking
>   endif
>   Reboot
>   Get good response
>ENDDO