The information in this article applies to:
SYMPTOMSAn application running as an executable that frequently calls a BROWSE and SEEK command progressively gets slower after several iterations. CAUSEVisual FoxPro is not releasing memory properly. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0b for Windows. MORE INFORMATIONSteps to Reproduce Problem
Additional query words: kbdsd VFoxWin
Keywords : FxprgBrowse |
Last Reviewed: December 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |