Article ID: 818178 - Last Review: March 11, 2005 - Revision: 2.2

Description of the memory leak bugs and the corruption bugs that are fixed in Microsoft Visual FoxPro 8.0

Expand all | Collapse all

SUMMARY

This article lists the memory leak bugs and the corruption bugs that are fixed in Microsoft Visual FoxPro 8.0.

MORE INFORMATION

List of Fixed Memory Leak Bugs


  • Memory Leak with FOR EACH Loop on Project Files Collection
  • Memory Leak in Table Wizard
  • Memory Leak with Repeated SELECT- SQL Statements from Offline Views
  • Memory Leak Changing Value When Text Box ControlSource Property Set to Form Property
  • OLE DB Provider Memory Leak Calling Stored Procedure Which Opens and Closes Table with Multiple Index Tags
  • Select Into Array in Stored Procedure Leaves Open Extra Temp Cursor for Each Select in OLEDB Provider
  • Memory Leak with Project Files.Add Method and Locals Window Open
  • Memory Leak with SQL-UNION When the Result Is "Not Union Compatible"
  • 'Not Enough Memory to Complete Operation' Error with SELECT with Complex Filter in JOIN Clause
  • Memory Leak with RESTORE FROM if Array Is Restored with String Element Greater Than 254 Bytes Long
  • Running Form That Returns .F. from Load Event Causes Memory Leak
  • Memory Leak Issuing Repeated CREATE SQL VIEW ... REMOTE Commands
  • Memory Leak Repeatedly Editing Remote View in View Designer
  • Memory Leak When Bound to ControlSource Which Is Character Member Property in CommandGroup Object

List of Fixed Corruption Bugs


  • Visual FoxPro Does Not Report Error When Command Causes Table to Exceed 2 GB Limit
  • Data Disappear from Offline View If It Is Closed and Opened Again During Transaction
  • Inserts Made Into Offline View During Transaction Are Not Committed by END TRANSACTION.
  • Incorrect Result from SQL Statement with Subquery That Returns More Than One Record

APPLIES TO
  • Microsoft Visual FoxPro 8.0 Professional Edition
Keywords: 
kbinfo KB818178
 

Article Translations

 

Related Support Centers