We have the same problem at some of our client sites. When they try and start a VFP 8 application on a few W2K computers they get:

Fatal error: Exception code=C0000005 @ 01/20/05 02:47:47 PM. Error log file: C:\Program Files\Common Files\Microsoft Shared\VFP\vfp8rerr.log

Usually if they log in as Administrator it works fine. Frequently logging in as another user will work also. The same application ran fine under VFP 7. It is not real common. Of the few hundred users we have this has been reported on about 10 computers so far.

Apparently it has to do with Roaming Profiles that have also been used on Windows XP. I passed this information on to the client sites and they confirmed it fixed the problem for them.

I found the information on it at this link:

http://groups-beta.google.com/group/microsoft.public.fox.vfp.setup.environment/browse_frm/thread/176ec0270f300d30?hl=en&lr=&ie=UTF-8&oe=UTF-8&rnum=1&prev=/groups%3Fq%3Ddropshadow%2Bgroup:microsoft.public.fox.vfp.setup.environment%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group%3Dmicrosoft.public.fox.vfp.setup.environment%26selm%3DaQlMJEw1DHA.3532%2540cpmsftngxa07.phx.gbl%26rnum%3D1

The relavent part of the message is pasted below. It is from:

Newsgroups: microsoft.public.fox.vfp.setup.environment
From: L...@online.microsoft.com (Lee Mitchell)
Date: Fri, 09 Jan 2004 22:36:24 GMT
Subject: Re: VFP8 gives FXError using User/domain

...

The reason that VFP 8.0 cannot run on a Windows 2000 computer after the
roaming profile has been used on a Windows XP computer is because we can
not register the window class it needs because we added a check for
Dropshadow effects on the XP machine. This should return 0 since it is XP+
only but for some reason it returns enabled with the roaming profile
active. There would be a couple of workarounds:

1. Disable all DropShadow effects in XP before logging off. You can do that from My Computer->Properties->Advanced->Performance Settings-> Adjust
for best performance or unselect anything that has to do shadows.

2. Run this code somehow to change it. You could create a startup script
for him to run his app:
ntemp=0
SystemParametersInfo(0x103F,0,ntemp,2)
...

Hope this helps.