Hi Doug,


We just started encountering a similar problem with a customer that updated to a dual 2.4 ghz Xenon processor server running Win2k SP3.

Our FPW 2.6a apps show the foxpro clock on the application and it slows down noticeably compared
to the system clock shown on the system task bar when we run them directly on the server. Appears that the system clock is about 3 to 4 times faster than the foxpro clock shown on the application.

The application is blazingly fast when run on the server, but timed events that rely on TIME() offsets don't fire correctly due to the slow TIME().

Don't have any solution yet, but you are not alone.


>We have recently began configuring Windows NT 4.0 SP6 servers that jumped from 1.8Ghz to 2.4Ghz processors. We have found that FoxPro applications keep pausing or hanging on the 2.4Ghz systems. Moving the same programs and data back to a 1.8Ghz system revealed them working normally again. We also found that the programs and data operate fine from a workstation...using the 2.4Ghz server as just a simple file server. Has anyone encountered this issue related to clock-speed? Any solutions found?