Memory exception bugs that are fixed in Visual FoxPro 9.0 (894009)



The information in this article applies to:

  • Microsoft Visual FoxPro 9.0 Professional Edition

SUMMARY

This article lists some of the memory exception bugs that are fixed in Microsoft Visual FoxPro 9.0.

MORE INFORMATION

The following memory exceptions caused earlier versions of Microsoft Visual FoxPro to stop responding (hang) or crash but are resolved in Visual FoxPro 9.0:
  • Visual FoxPro crashes with a memory exception error when you save a form to a folder that you do not have delete permissions for.
  • An infinite loop in the INDEXSEEK() function in a multi-user scenario causes Visual FoxPro to stop responding.
  • Visual FoxPro crashes with a memory exception error when a semicolon (:) is used in the cFileExtensions parameter of the PUTFILE() function.
  • Visual FoxPro crashes with a memory exception error when the TRACE window is open and you expect a "Syntax Error" error message because of a bad class definition.
  • Visual FoxPro crashes with a memory exception error when the ASSERT command calls the MESSAGE() function and tries to display more than 32,000 characters.
  • Visual FoxPro crashes with a memory exception error when you run a SQL SELECT command against a table with a Memo field and that table is not open exclusivly.
  • Visual FoxPro crashes with a memory exception error when you access objects in a control array by using the "THIS" keyword.
  • Visual FoxPro crashes with a memory exception error in the View Designer when you access field properties on a view to a Microsoft Office Access table and the field name contains a space.
  • Visual FoxPro crashes with a memory exception error when you concatenate a long string as the value of a class property.
  • Visual FoxPro crashes with a memory exception error when code uses the ALINES() function.
  • Visual FoxPro crashes with a memory exception error when the following conditions are true:
    • You set the MemberClass property to a class.
    • That class is in a program that has 100,000 class definitions.
  • You receive an "Invalid File Descriptor" error message and then Visual FoxPro crashes with a memory exception error. This behavior occurs when you save a program by pressing CTRL+ENTER when the program is being viewed at the same time by a third-party file viewer.
  • Visual FoxPro crashes with a memory exception error in Report Designer when you use TAB and SHIFT+TAB keyboard navigation.
  • Visual FoxPro crashes with a memory exception error when you run code that includes SQL SELECT commands, parentheses, and subqueries.
  • Visual FoxPro crashes with a memory exception error in a label object when the following conditions are true:
    • The MouseEnter event contains a call to a delegate.
    • The delegate sets the FontBold and FontUnderLine properties by using an AEVENTS() function array member reference.
  • Visual FoxPro crashes with a memory exception error when you access Microsoft IntelliSense for the ADODB DataSource object.
  • In the Import Wizard, you receive an "Error # 230 in CreateCursor (0)" error message and then Visual FoxPro crashes.
  • You use the IN clause with a subquery in a SQL SELECT statement. If the subquery returns a constant value, an incorrect result is produced or you receive an 80000003 exception.
  • If you close an alias in a SELECT UDF(field) command, a general protection fault occurs.
  • You receive an internal consistency error message when you close a form that has a private data environment and that private data environment contains a cursor adapter that is used in another form.
  • Visual FoxPro crashes with a memory exception error when you append from another table referenced by the DBF() function while a Browse window is open on the table identified in the DBF() function.
  • Visual FoxPro crashes with a memory exception error when the following conditions are true:
    • You click View Code in the Class Browser on a specific .vcx-based class library.
    • The Document View window is open.
  • Visual FoxPro crashes with a memory exception error if the SYS(3055) setting is enlarged during SQL execution.
  • Visual FoxPro crashes with a memory exception error when the following conditions are true:
    • In a Visual FoxPro code editing window, you run code by clicking Execute Selection in the shortcut menu.
    • The code contains a CLEAR EVENTS command.
  • Visual FoxPro crashes with a memory exception error when the Destroy() event opens a project as part of the QUIT shutdown process.
  • Visual FoxPro crashes with a memory exception in a program when you clear a user-defined submenu.

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

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


Modification Type:MinorLast Reviewed:11/18/2005
Keywords:kbinfo KB894009 kbAudDeveloper