KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q156507: HOWTO: Bypass Registry Settings on Visual FoxPro Startup

Article: Q156507
Product(s): Microsoft FoxPro
Version(s): WINDOWS:5.0,6.0
Operating System(s): 
Keyword(s): kbnokeyword kbvfp500 kbvfp600
Last Modified: 26-MAY-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Visual FoxPro for Windows, versions 5.0, 6.0 
-------------------------------------------------------------------------------

SUMMARY
=======

In Visual FoxPro 5.0 and 6.0, a new command line switch, -A, is available for
starting a Visual FoxPro session while ignoring all the settings in the Windows
registry.

MORE INFORMATION
================

If an invalid or corrupt registry is suspected, you can start Visual FoxPro
without invoking the Windows registry settings.

For example, use the following steps in Windows 95 or Windows NT 4.0:

1. On the Start menu, click Run.

2. Enter the path to a Visual FoxPro program: C:\VFP50\VFP.EXE -A

3. Click OK.

Use the following steps in Windows NT 3.51 using Visual FoxPro 5.0:

1. On the File menu, click Run.

2. Enter the path to a Visual FoxPro program: C:\VFP50\VFP.EXE -A

3. Click OK.

NOTE: In the preceding example, your registry settings are not invoked upon
Visual FoxPro startup.


Additional query words:

======================================================================
Keywords          : kbnokeyword kbvfp500 kbvfp600 
Technology        : kbVFPsearch kbAudDeveloper kbVFP500 kbVFP600
Version           : WINDOWS:5.0,6.0
Issue type        : kbhowto

=============================================================================

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.