>>My department is in the process of "upgrading" from Windows 95 to Windows NT. We develop in FoxPro 2.6a for Windows. After I reinstalled FPW26 on my new Windows NT machine, I tried to run it. 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?
>>
>>Thanks for any help you can give.
>>
>>Dan Rhymes
>
>Dan,
>Something else I have just found using FPW2.6 on WinNT - if you run long apps (we have an app running 24 hours a day) the time will get messed up. I had to run it temporarily on my PC (normally runs on a 95 machine) and left it running overnight - when I got in at 7.30am the next day, my clock in FoxPro session showed 01:15 although my taskbar clock (NT) showed the correct time. I noticed that all calls to time showed incorrect but calls to date() showed correct. This app logged the time constantly. Some logs showed 18 hours ahead. When the W95 PC was fixed, I put it back on there and it runs fine! Beware!!!

Thanks Nigel,

I'll keep this in mind. I'll more-than-likely be writing some time-sensitive programs in the near future.

Dan