>If anybody is thinking of running 2.6 apps on Windows NT, I have found a problem if you run long apps. We have a 2.6 app which runs 24 hours a day copying/logging files. The time seems to drag at the rate of about 16 hours each day. If you run an app for 24 hours, the time in the FoxPro session will only advance 8 hours! If you call TIME() it will show the session time, not the PC time (which is still correct). However, if you call DATE() it will return the correct date.
>This same app works perfectly well under W95.

Hey I've seen this too with my 2.6 app. But TIME() isn't used in my code so I don't worry about it unless I'm monitoring performance. Also, a few months back I upgraded the memory in my NT4.0 server from 64 to 128MB and the drag became alot less obvious.