Microsoft KB Archive/818175

= List of memory exception bugs that are fixed in Visual FoxPro 8.0 =

Article ID: 818175

Article Last Modified on 1/25/2005

-

APPLIES TO


 * Microsoft Visual FoxPro 8.0 Professional Edition

-



SUMMARY
This article lists the memory exception bugs that are fixed in Microsoft Visual FoxPro 8.0.



List of fixed memory exception bugs

 * Fatal Exception Using with SCAN...ENDSCAN on Table with Corrupted Index Tag Using DELETED
 * Fatal Exception with Excel Spreadsheet and IMPORT Command
 * Fatal Exception When You Use View with Subselect Against View
 * Fatal Exception When You Close Preview Window in Report from Table with Index on Missing PRG
 * Fatal Exception Occurs When You Recursively Call EVALUATE or TEXTMERGE
 * Fatal Exception Occurs When you Click in Properties Window after You Call RemoveObject of Selected Object in Form Designer
 * Fatal Exception When You Instantiate a VCX Class with Hidden Property Set to an Expression
 * Fatal Exception Occurs with DOEVENTS in ComboBox MouseDown Event When You Click Scrollbar
 * Fatal Exception Occurs When You Set Picture Property to Corrupted JPEG File
 * Fatal Exception Occurs When You Close Form Designer with Reference to Data Environment Cursor in Locals Window Created by ASELOBJ
 * Fatal Exception with ExecScript(&quot;&quot;) in Watch Window
 * Fatal Exception with REQUERY of RecordSource in Grid Init Method
 * Resource Manager Internal Consistency Error with Locals or Watch Window and Container with Many Image Controls
 * Fatal Exception with ACTIVATE WINDOW DOCUMENT in Startup Program
 * Fatal Exception on ACTIVATE POPUP with Class Designer, Properties Window, and Controls Toolbar Active
 * Fatal Exception or Visual FoxPro Exits upon Resume after Suspend or Breakpoint
 * Fatal Exception with Invalid Grid Column.ControlSource and Code in Form Unload Method
 * Fatal Exception Closing Project Manager When Suspended in Project Hook Code Then Resuming
 * Connectivity Internal Consistency Error When UPPER('(A') in Select- SQL Statement
 * Fatal Exception Invoking Menu When Bar with No PROMPT Has Popup
 * Fatal Exception with SaveAsClass on Created Object
 * Fatal Exception Setting Object Reference to Form Object Three Times Using Assign Method
 * Fatal Exception When Setting Object Reference to Null
 * Fatal Exception Using CREATE CLASS and Saving to VCX with Name Longer Than 256 Characters
 * Fatal Exception Clicking Project Manager Modify Button Then Run Toolbar Button for Form
 * Client Application Exits Using Visual FoxPro OLE DB Provider if Long Connect String Passed to RS.Open
 * Fatal Exception if MessageBox with TIMEOUT Clause Called from Project Hook QueryNewFile Method
 * Fatal Exception with Debug/Fix after &quot;Remove Classes from Memory&quot; in Complex Application
 * Fatal Exception Displaying QuickInfo for Procedure with 27 Parameters
 * Fatal Exception with UPDATE - SQL Statement to Memo Field with Carriage Return and Line Feed Characters
 * Fatal Exception with CLEAR CLASS of Text Box in Grid Column from Released Form
 * Fatal Exception Typing Open Parenthesis after User Defined Method Name with IntelliSense
 * Fatal Exception or “File Is Not Open” Hang with Step Into in Trace Window after SET STEP ON in ExecScript Call
 * Fatal Exception When FOXUSER.DBF Breakpoints Information Data Is Modified
 * Fatal Exception Assigning a Numeric Value to a Column ControlSource
 * Fatal Exception When CommandGroup Properties Is Set Incorrectly
 * Fatal Exception Assigning (1) to Separator.Style Property
 * Visual FoxPro Exits after Assigning Large String to Format Property of Column
 * Fatal Exception or End Task after VALIDATE DATABASE RECOVER Gives &quot;Index Does Not Match the Table&quot; Error
 * Fatal Exception on Report Preview in Visual FoxPro 7.0
 * Visual FoxPro Exits after Nested Replicate Calls
 * Fatal Exception in Preview with Report That Calls User-defined Functions
 * Fatal Exception or “Not Enough Memory” Error or Visual FoxPro Disappears after Deleting Grid Columns
 * Fatal Exception on Editbox Refresh with Traditional Chinese Operating System Settings in Windows 2000 or Windows XP
 * SELECT Calling a User-Defined Function That Returns Object Causes Internal Consistency Error (ICE) and Then Visual FoxPro Exits
 * Fatal Exception with SET DEFAULT TO Extended ASCII Character String
 * Fatal Exception When Releasing Top-Level Form with Docked Toolbars Saved as Object References to Form Properties
 * Fatal Exception When Repeatedly Removing and Re-adding Columns to a Grid
 * Fatal Exception with USE Command with CONNSTRING Keyword with Shared Connection
 * Fatal Exception in the View Designer When Using a Field Without Table Prefix in Remote View
 * Fatal Exception When Rebuilding Foxcode.app if Intellisense Manager Is Open
 * Fatal Exception with Repeated Calls to TEXTMERGE Function
 * Fatal Exception Assigning the _VFP Object to Custom Property with SETALL
 * Fatal Exception When SQL SELECT Used with Long Table, Field, Alias Names and SYS(3054,12)
 * Calling ALINES Repeatedly with Extra CHR(13) Terminator Causes Fatal Exception
 * Fatal Exception in Form Designer When Changing ScaleMode Property of Form after Adding and Removing Object
 * Fatal Exception When Passing Long Connection String to SQLSTRINGCONNECT Function
 * Visual FoxPro Exits When Passing Large String to TXTWIDTH
 * Fatal Exception Passing Large String to CREATEOFFLINE
 * Visual FoxPro Exits When Passing Large Strings to GETOBJECT
 * Fatal Exception with ResetToDefault on a Property Added with ADDOBJECT
 * Fatal Exception on ROLLBACK Command after Offline View Is Opened Online
 * Fatal Exception with COPY TO after Using SET FIELDS to a Calculated Field
 * Fatal Exception When You Print a .PRG file from Windows Explorer
 * Fatal Exception Editing a Label Caption with More Than 255 Characters
 * Fatal Exception When Using Very Long Array Name with Array Functions
 * Fatal Exception Running SUM Command
 * Fatal Exception When Moving Mouse Over _SCREEN Variable and Object Reference in Trace Window
 * Fatal Exception When BROWSE Window Is Closed While It Is Running External Code 22553
 * Fatal Exception When ROLLBACK Restores Table Buffer Incorrectly with Table Opened Two TImes Table Buffering
 * Fatal Exception When You Repeatedly Add and Remove Columns in Read Only Grid
 * Fatal Exception with PACK if Other Users Are Trying to Access the Table
 * Fatal Exception When You Close the Toolbar after You Set Focus to Text Box in Another Toolbar
 * Fatal Exception When Two Indexes Have the Same Name in Database Designer
 * Fatal Exception When You Set Cursor.CursorSource Property to Long String
 * Fatal Exception When You Repeatedly Right-Click in Document View Window
 * Fatal Exception When You Use SELECT-SQL and JOIN with Complex Filter
 * Error in Expression Builder with EXECSCRIPT Function May Cause Fatal Exception
 * Executing Code in Editor with Properties Window Open May Cause Fatal Exception
 * Fatal Exception May Occur After Running then Editing Form with a ComboBox That Has Large Number of Pictures
 * Exiting Complex Application Because of an Error Causes Fatal Exception
 * Fatal Exception Occurs When You Insert a New Value in the BROWSE Window Where the Default Value Is the Command CLEAR ALL
 * Fatal Exception if Table Is Closed or Not Opened While Report Preview Window Is Open
 * Fatal Exception Occurs When Sub-SELECT Incorrectly References A Table In Main SELECT
 * Internal Consistency Error When Changing Toolbar Button Size after Adding a Form to a Formset
 * Fatal Exception When Using GROUP BY and Expressions in Field List
 * Fatal Exception Occurs When Closing Tables Added Programmatically to the Data Environment of a Form in the BeforeOpenTables Event
 * Internal Consistency Error if Private or Local Variables Are Used in the Destroy Event
 * Fatal Exception Occurs When Print Preview Is Open and Class Is Created
 * Fatal Exception When You Close Form Designer with Two Form Designer Instances Open

Keywords: kbinfo KB818175

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.