List of Problems Solved by FoxPro 2.6a for Windows

Last reviewed: May 27, 1997
Article ID: Q148836
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6a

SUMMARY

This article lists the problems in FoxPro version 2.6 for Windows that were corrected in FoxPro version 2.6a for Windows.

MORE INFORMATION

This list contains the numbers and titles of Microsoft Knowledge Base articles that fully describe the problems corrected in FoxPro 2.6a for Windows:

Knowledge Base Articles

 Q102463 FIX: Incorrect Group Footer Sum Using Previous in Preview
 Q108637 FIX: MODIFY REPORT from .EXE Causes Internal Consistency Err
 Q108823 FIX: Issuing FONTMETRIC() Repeatedly Causes ICE/GPF
 Q109581 FIX: SELECT ... UNION Produces Unexpected Output

 Q110969 FIX: Reports Executed from Loop Cause "Insufficient Memory"
 Q111526 FIX: Print Range Incorrect with Stretched Group Footer field
 Q112834 FIX: #IF and #ENDIF Behavior in FoxPro Differs from dBASE
 Q113798 FIX: "Invalid Library" When Rebuilding an Application
 Q114142 FIX: Resizing Band in Report Causes General Protection Fault

 Q114145 FIX: Index Doesn't Match Table When Opening dBASE Table
 Q114146 FIX: "Conversion Cancelled. Adjust Memo BLOCKSIZE"
 Q114174 FIX: Wizards Fail If Path Is Longer Than 38 Characters
 Q114176 FIX: Error Occurs When Wrong File Added to Catalog Manager
 Q114191 FIX: LASTKEY() Returns 13 When Left Mouse Button Is Pressed

 Q114270 FIX: CTOD() and VAL() Functions Are Not Saved in Query
 Q114289 FIX: "Unrecognized Phrase/Keyword" Error with @ ... SCROLL
 Q114497 FIX: CLOSE PRINTER Command Is Not Supported
 Q115264 FIX: COPY TO Incorrectly Copies All Fields to New Database
 Q117710 FIX: FoxPro for Windows Can't Load .BIN Files Over 32K

 Q118741 FIX: "Internal Consistency Error" in RQBE with ISBLANK()
 Q118848 FIX: Project Asks to Locate BMP/PCT When Rebuilding
 Q119228 FIX: LASTKEY() Doesn't Recognize Click in WAIT WINDOW
 Q119251 FIX: Relationship Between Tables May Cause ICE or GPF
 Q119695 FIX: ON ERROR Routine Causes "Feature Not Available" Message

 Q119761 FIX: SET CPCOMPILE w/ Invalid Code Page Sets CPCOMPILE to 0
 Q119902 FIX: ALIAS() & SELECT() Browse Results Not Consistent w/2.5x
 Q119939 FIX: Screen Builder Doesn't Recognize #ELIF & #UNDEF
 Q120179 FIX: Insufficient Stack Space Hangs or Terminates FoxPro
 Q120189 FIX: "Paging Error" with DDEPOKE and String Greater Than 64K

 Q120191 FIX: Variable Not Created by ON KEY or ON ERROR
 Q120695 FIX: LOAD <Name> FUNCTION Produces Compiler Error
 Q121088 FIX: AutoScreen of Extremely Wide Table Causes Error
 Q121634 FIX: Screen Choice Not Staying Selected in Catalog Manager
 Q122270 FIX: RQBE Quick Report Shows All Fields Not Just Selected Ones

 Q122588 FIX: TRANSPRT.PRG Gives Wrong Message Converting dBASE Report
 Q122590 FIX: dBASE Message Clause Incorrectly Converted by MIGRATE.APP
 Q122791 Query Keywords Specific to the FoxPro Knowledge Base
 Q122865 FIX: SQL Query Wizard Via CatMan Truncates Cursor Name
 Q124163 FIX: INSERT BEFORE Overwrites Data

 Q124274 FIX:Internal Consistency Error If MODIFY REPORT to Add Comment
 Q124300 FIX: Browse Format Ignores GET/SAYs with Color Clause
 Q124325 FIX: Insufficient Stack Space Error When Press ENTER then ESC
 Q124328 FIX: GP Fault When Clear Debug Window That Has Open Memo Field
 Q124362 FIX: SET SYSMENU TO DEFAULT Command in Program Clears Menu

 Q124595 FIX: APPEND NOMENU Not Recognized in FoxPro
 Q124672 FIX: GPF When Inserting an Object in a General Field
 Q124777 FIX: Printing Report Writer Lines with HP Laserjet 4 Drivers
 

	
	


Keywords : fixlist2.60a FoxWin FxotherReference kbfixlist kbref
Version : 2.6a
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.