>>>Hi,
>>>
>>>I got a message from a customer that the feature that always worked, now, for all users gives the error message:
>>>
>>>

>>>AppName has stopped working
>>>A problem caused the program to stop working correctly.
>>>Windows will close the program and notify you if the solution is available
>>>

>>>
>>>It appears that the message comes from Windows, not for the application. I don't get this error.
>>>
>>>Where would you suggest I ask the customer to look? He wrote, all user, this is puzzling.
>>>
>>>TIA
>>
>>I got something like this when a .NET program of mine ran a long time with no user interaction.
>>Windows thinks it's in a loop and stops it.
>>I solved it by using a background helper.
>
>This is a VFP 9 application, not .NET. From the message of the user, the problem happened immediately when he clicked on the button. It could be that the problem has the same bases though.
>I wrote to him to shutdown the PC and restart. Hopefully he will let me know of the result.
>And since the problem is with all their users and they all use the app from their desktops, I suspect that the SQL Server had a glitch.
>Thank you.

That message could occur with a VFP application -- you tend to get it if your program is in a long-running processing loop w/o interaction with the user.

I did run into this sort of issue a long while back (with some code with origin dating back to the DOS days) with some code that was interacting with some hardware. There was a "busy-wait" loop: that needed to be changed:

DO WHILE NOT hardware_ready()
    * Do nothing
ENDO

to something along the lines of

DO WHILE NOT hardware_ready()
    SystemSleep()
ENDDO

where SystemSleep() would be code that would relinquishes the current timeslice. In FoxPro that would be the DOEVENTS statement.