>Check if the error produces a log file in C:\Program Files (x86)\Common Files\Microsoft Shared\VFP
>
>Sometimes that produces some information that can at least show you which method raised the error.

I've got one or two, but the linenumbers do not make any sense. One was a

THIS.BorderStyle = 0

They already have updated the graphics card driver. Not much to go on here.

Walter,


>
>>Hi All,
>>
>>Just in one week time we have two customers who have upgraded their workstations to Windows 10 calling for support because of our application errors out with a C5. The point of where it happens seems to be random.
>>
>>So far I have advised them to
>>- Check the network driver
>>- Check the printer driver and test while a different printer is the default printer
>>- Check the graphics driver and upgrade that if needed
>>- Disable the virus scanner temporarily to see whether it makes a difference
>>
>>- Delete the user profile on that machine and restart Windows
>>
>>Though I'm not able to check whether they all try that, it sounds like the problems are still there.
>>
>>This application has been very stable so far, and this particular build has been running on hundreds of workstations without a problemin the past, so I pretty much rule out it is our application.
>>We are running our application with SET RESOURCE OFF, so it also does not have anything to do with foxusers.dbf
>>
>>
>>Does anyone have the same experience with Windows 10 and a VFP9 app ?
>>
>>
>>Walter,