PRB: DoDefault() in Command Window Stops Visual FoxPro

Last reviewed: October 10, 1997
Article ID: Q174967

The information in this article applies to:

Microsoft Visual FoxPro for Windows, version 5.0a

SYMPTOMS

Typing DoDefault() in the Command window causes an application error in Visual FoxPro version 5.0a. In Windows 95, the error message below appears:

   This program performed an illegal operation and will be shut down.

After pressing the Details push button, the following message appears:

VFP caused and invalid pagefault in module VFP .EXE at <register

   address>.

In Windows NT 4.0, the following error appears:

   An application error had occurred and an application error log is
   being generated.
   VFP.EXE
   Exception: access violation.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This also occurs with Visual Studio 97 Service Pack 2 installed. In Visual FoxPro version 5.0, typing DoDefault() in Command window error produces the following error message:

   Statement is only valid within a Method

Steps to Reproduce Behavior

In the Command window, type in the following command:
```
      DoDefault()
```

NOTE: Visual FoxPro version 5.0a stops immediately after you press Enter.

Additional query words: Dodefault GPF Invalid Page Fault Application Error
Unhandled exception
Keywords : FxprgGeneral vfoxwin kberrmsg
Version : WINDOWS:5.0a
Platform : WINDOWS
Issue type : kbprb

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: October 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.