Hi Sergey,

Thanks for the pointer, looks like the same thing that in VFP's help. What happened was that I was getting a "not enough memory error" when I attempted to load VFP on my home computer. It's got W2K pro on it. I had installed SP1 the day before, all seemed ok when I shut it down at the end of the day. My wife was also using the system for some stuff so when I attempted to load VFP and got the error I wasn't certain what caused the error.

I ended up un/reinstalling VFP7 and then I got a C00000FD error (several times) and VFP would not load again. I added -a to the shortcut and VFP loaded and appears to load without error. Oddly during this time of error I was able to get into VPM7 without error and was able to get to and work from the VFP command window.

Got any Ideas?


>http://msdn.microsoft.com/library/en-us/fox7help/html/conCommand_Line_Switches.asp?
>
>>Hi Craig,
>>
>>What does the /a switch do?
>>
>>>I'm wondering if there's a problem with the registry settings. Try launching VFP with the /a switch and see if you still get the GPF.
>>>
>>>
>>>>I started getting a Exception code=C00000FD today when I start VFP7. I’ve been using VFP7 for about 3 months without incident. I deleted my FoxUser.dbf and .fpt files and the error goes away. As I start adding functionality and the error surfaces again.
>>>>
>>>>Deleting the FoxUser files and starting from scratch, if I add the report designer toolbar and dock it on the left side, doing nothing else, it errors again.
>>>>
>>>>After messing with that for a while I discovered that Fox was opening Maximized and when set to Normal, it no longer existed on the desktop. Fortunately using the default startup of VFP7 the command window is set dockable and is the only thing left on the desktop. I was able to restore the fox workspace onto the desktop using:
>>>>
>>>>

_screen.Top=175
>>>>_screen.left=175
>>>>_screen.Height=500
>>>>_screen.Width=800
>>>>_screen.WindowState= 0

>>>>
>>>>It appears something took place that messed with the _screen settings causing the C00000FD. I have a hunch that somehow IE6 is involved. Nothing I can point to, just a suspicion. Is this a known issue or am I just lucky?