The information in this article applies to:
SYMPTOMSWhen you issue commands such as INDEX, REPLACE ALL, or PACK, some computers may take a long time to finish processing the results. This only occurs if the computer is running the Windows NT 4.0 operating system. Also, the faster the computer and the more RAM that is installed, the more time that it takes for the computer to finish the command's tasks. Visual FoxPro also shows as "Not Responding" in the Application tab of the Task Manager, but in fact, is working to complete the task. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. MORE INFORMATIONIn testing this, it seems that setting SYS(3050) to 1 MG seems to decrease the time it takes to finish these tasks. Try this command before issuing the other commands listed in this article.
FoxPro can normally process one of the commands listed in the SYMPTOMS
section in a very short time, even on a large table. However, on several of
the new faster computers, Visual FoxPro slows down drastically when
processing these commands. The computers that seem to have this problem are
233 MHz and up, and have at least 64 MB of RAM. It has been reported that
200 MHz computers also display this behavior, but the sluggishness is more
pronounced as the speed and amount of RAM of the computer increases.
Another way to observe that the computer is struggling to process the command, is to open the Windows NT Task Manager, click the Applications tab and note that Visual FoxPro is "Not Responding". During the whole process, the hard drive of the computer runs constantly, trying to finish the task. Steps to Reproduce Behavior
Additional query words: FxPrgTable kbvfp600
Keywords : FxprgTable |
Last Reviewed: July 12, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |