>>It looked like NT tried to open it - the FPW splash screen came up with the FPW desktop behind it and then FoxPro immediately closed down.
>>
>>Has anyone had these kind of problems? If so, how were they resolved?
>
>Hi Dan,
>I've seen this before, it is probably one of two things...
>
>The first one is easy, FPW2.6 needs to have "Run in Separate Memory Space" turned on for each instance of an application and/or the software itself. You set this under properties for a shortcut to app/software. The setting is specific to the current username, so if the machine gets different login names, you need to make sure each user has the setting turned on. The other situation where I seen something similar to your problem happen was when the network administrator reloaded NT and forgot to install some hot fixes/patches for whatever the current Service Pack was at the time. Once the Service Pack was loaded properly, everything was cool again. HTH

Roxanne,

Thanks for the information. Our "network guys" reloaded NT. And all is well (for the time being).

Dan