We are executing Visual FoxPro programs at specific times using a product called TimeTarget (Scheduler) to launch to VFP 7.0 compiled programs at off-hours. The machine that launches these programs is a Windows 2000 machine; this machine runs fine. The one major program we are running on the Win2k machine is one that downloads Purchase orders and this is the 1st of a 2-step process.

The 2nd step of the Download of PO's is executed on a Windows XP Professional machine in Southern California; that machine has Service Pack 1 installed. We have Drive disconnections now that we didn't have before Sevice Pack 1 and our processes therefore fail, having depended on mapped drives to tables in the south and the north (of Calfornia). This whole process used to run perfectly.

There are rumors that Windows XP Service Pack 1 makes worse the XP Operating System. I have to admit that our processes were running almost perfectly prior to the installation of XP SP1.

Would anyone happen to know why Windows XP screws up communications so badly, or has anyone had experience with this? Also, the connection between the two sites is on a T-1 and the drive is mapped as Drive N:\. We can access Northern California files on this server by accessing drive N:\. Even after we receive the error message that the network path cannot be found, we are still able to access that drive in some cases, but the immediate process fails momentarily, which is all it takes to kill it entirely.

Obviously, this is not a FoxPro problem, but an operating system problem.

Any ideas? Has anyone had experience with Windows XP Professional?

Thanks,

Cecil