It would be interesting if you create a new user, and see if will work. In that case, the problems may be related.

Steven

>I am having a similar problem on my Win2K machine. When I try to run FoxPro for Windows 2.6, it displays the splash screen and the main window for about two seconds and then quits. No error message, it just quits. Other developers and users can run it just fine on their Win2K machines. Mine seems to be the only one with this problem. Our support people are trying to find the difference in my machine. One clue is that when I try to start FoxPro it also shuts down another DOS app called "HotKey" that I run from my Startup menu. I can restart Hotkey again with no problem.
>
>>As the foxuser is located in the directory where FoxPro is starting up, I cannot see that there would be a difference if I zapped the file. What I mean is that if I log on as another user, it would be the same foxuser file that would be used, so why would it suddenly work? If every user that logged in had a different foxuser, then it would make perfect sense, but that is not the case.
>>
>>I will try it though and will let you know if it helped.
>>
>>There is no error message whatsoever, Foxpro just terminates.
>>
>>STeven
>>
>>>Hi Steven,
>>>
>>>>Also, how do I explain that if I create a new user it works again? >Obviously it has something to do with settings particular to a certain user.
>>>
>>>>Another strange effect of the problem is that on compiled files everything >goes well until I run a report. Then the whole application terminates, just >in the same way as when I open a screen in the screen designer from FoxPro.
>>>
>>>could be foxuser-related. how about a zap there and testing the "old" users ?
>>>
>>>>>.. at least once a week or so Fox throws an unhandled exception error and closes down.
>>>
>>>If this is "Error in modul Noname" it might be memory-related.
>>>
>>>HTH
>>>
>>>thomas