>>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?
>
>A workaround to fix this bug, as it seems to be one, a timer can do refresh of the status bar after your process by putting it ON/OFF or a technique similar to this.
>
>Just curious, if there is the clock on the taskbar, why having another one on the Visual FoxPro status bar. :)

It's 2.6 - not Visual. No timer. The app runs as one of three on a single machine (or it did 'til last night). They used to run on Win3.1 so the taskbar clock is a bonus in Win95 (it helped here). I'll try the clock on/off route between passes - it's a continuous program constantly looking for files.