How the Catalog Manager Locates Wizard Files

Last reviewed: June 27, 1995
Article ID: Q115037
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, version 2.6
  • Microsoft FoxPro for Windows, version 2.6

SUMMARY

This article documents the steps followed by the Catalog Manager when it is needs to search for a wizard file. Knowledge of the manner in which the Catalog Manager searches for wizard files can be helpful when troubleshooting behavioral problems.

MORE INFORMATION

When a wizard is invoked from within the Catalog Manager, the Catalog Manager must invoke WIZARD.APP. Once WIZARD.APP is invoked by the Catalog Manager, it will invoke the desired wizard. The Catalog Manager follows these steps when it needs to invoke WIZARD.APP:

  1. Look for an entry in the resource file where the ID field contains "CATALOG" and the Name field contains "WIZARD.APP Path".

  2. Then do one of the following, depending on whether the entry exists:

        - If the entry described in step 1 exists, search for WIZARD.APP in the
          location specified in the Data field. If WIZARD.APP exists at the
          location specified in the Data field, WIZARD.APP will be invoked. If
          WIZARD.APP does not exist at the location specified in the Data
          field, look for WIZARD.APP in the SYS(2004)+'\Wizards' directory. If
          WIZARD.APP exists in that location, the Catalog Manager will update
          the path to the WIZARD.APP file that is stored in the program field
          and will invoke WIZARD.APP. If WIZARD.APP does not exist in the
          SYS(2004)+'\Wizards' directory, the LOCFILE() dialog box will be
          invoked. If the user points to the location of the file for the
          desired wizard using the LOCFILE() dialog box, the resource file
          entry described in step 1 will then be created and the path to the
          file that was selected by the user will be stored in the program
          field.
    

          -or-
    

        - If the entry described in step 1 does not exist, look for WIZARD.APP
          in the SYS(2004)+'\Wizards' directory. If WIZARD.APP exists in that
          location, it will be invoked. The resource file entry described in
          step 1 will then be created. If WIZARD.APP does not exist in the
          SYS(2004)+'\Wizards' directory, the LOCFILE() dialog box will be
          invoked. If the user points to the location of the file for the
          desired wizard using the LOCFILE() dialog box, the resource file
          entry described in step 1 will then be created and the path to the
          file that was selected by the user will be stored in the program
          field.
    


Additional reference words: FoxDos FoxWin 2.60
KBCategory: kbother kbtshoot
KBSubcategory: FxtoolWizother


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: June 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.