Nigel,

Are you running FoxPro 2.6 under NT? It seems that NT's 16 bit virtual machine keeps time separately from the system clock. I had a problem with two applications running on one machine. One put the start time of a phone call in a table, the other put the end time in. We ran them on one machine so the times would synch. Well, they didn't. If they had both been running for several weeks, and you re-started one, the times would be off. This led to end times before start times (which were interpreted as 23 hour plus phone calls). We were billing for these calls by the minute so bad things happened!

>I have an app in 2.6 which scans 4 servers for existence of files and, if found, transfers files to a fifth server, updates a file on the fifth server with details, and renames the original file on the original server. This works fine. BUT, when the file copies, it slows down the clock in my FoxPro session. I started it last night and got in at 7.30 this morning. My taskbar clock said 7.30, my Fox session clock (status bar) said 01.00??? I stopped the app and the Fox session clock ticked at less than one second per second - when it finally caught up, it ticked at one second per second!!! This is very wierd. I intend to rewrite in Fox 5. Has anybody else come across this?