The information in this article applies to:
SYMPTOMSPrinting reports in loops generates an "Internal Consistency" error under Windows 95 and hangs Visual FoxPro under Windows NT 4.0. CAUSEThis activity causes massive amounts of spooling, which causes a low memory situation because of continuous virtual memory swapping. RESOLUTION
Create an out-of-process Visual FoxPro OLE server to handle the printing
and release the object when the printing is completed. This workaround is
available only in versions of Visual FoxPro later than 3.0x.
In your application, replace the REPORT FORM command with the following lines of code:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. MORE INFORMATIONWARNING: Close all running applications and save your data before following this procedure. Note that following these steps may produce lost allocation units, lost clusters, or cross-linked files. Steps to Reproduce Behavior
Additional query words: kbprint hang kbDSupport kbDSE VFP600REL kbvfp300 kbvfp300b kbvfp500 kbvfp500a kbvfp600
Keywords : |
Last Reviewed: August 3, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |