FIX: "Feature Not Available" from FPD 2.6 Stand-Alone .EXE

Last reviewed: October 20, 1997
Article ID: Q120288
2.60 MS-DOS kbprg kbbuglist kbfixlist kberrmsg

The information in this article applies to:

  • Microsoft FoxPro for MS-DOS, version 2.6

SYMPTOMS

When you are running a stand-alone executable (.EXE) file, if the program uses the BLANK command (which is new to FoxPro 2.6) or the SET PDSETUP command, an error dialog box containing the message "Feature not Available" appears, with Cancel and Ignore buttons.

However, the program will run successfully in the development environment, as an .APP, or as a compact executable file.

CAUSE

The function to compile the object code for the BLANK or the SET PDSETUP command into a stand-alone executable file does not work in the stand-alone compiler for FoxPro 2.6 for MS-DOS.

WORKAROUNDS

To work around this problem, do one of the following:

  • Use the REPLACE command to replace the contents of a field with a blank. For example:

          REPLACE <fieldname> WITH " "  && quotation, space, quotation
    

    NOTE: This command will blank a character field but not a numeric field.

    -or-

  • Substitute a compact executable file for the stand-alone executable file.

STATUS

Microsoft has confirmed this to be a problem in the FoxPro 2.6 for MS-DOS stand-alone compiler provided with the Distribution Kit included with the Professional Edition of FoxPro 2.6 for MS-DOS. This problem was corrected in the Professional Edition of FoxPro 2.6a for MS-DOS.

MORE INFORMATION

Steps to Reproduce the Problem

  1. Write a program called BLANKTST.PRG using the BLANK command, as follows:

          CREATE TABLE blanktst (First C(10))
          m.first="one"
          APPEND BLANK
          GATHER MEMVAR
          WAIT WINDOW "First = "+first
          BLANK ALL
          WAIT WINDOW "First = "+first
    

  2. Save the program, then execute it by typing "DO blanktst.prg" (without the quotation marks) in the Command window.

    The first WAIT window will display the string:

          First = one
    

    The second WAIT window will display the string:

          First =
    

  3. Create a project containing the program BLANKTST.PRG. Build the project, and then build an .APP file using the project. Run the .APP version of the program. The WAIT windows will display the same strings as shown above.

  4. Build a compact executable file using the project. Run the .EXE version of the program (BLANKTST.EXE). The WAIT windows will display the same strings as shown as above.

  5. Build a stand-alone executable file using the project. Quit FoxPro. Run the stand-alone executable file, either by double-clicking the BLANKTST.EXE file in the Windows File Manager, or by typing "BLANKTST" (without the quotation marks) at the MS-DOS command prompt.

    The first display of the WAIT window will be the same as the first line shown above.

  6. Press any key to move forward in the program.

The error dialog box will appear, stating "Feature not available." Choose the Ignore button. The program will continue, displaying the second WAIT window which will contain

   First = one

demonstrating that the BLANK command did not blank out the field.

For information about other commands that exhibit the same behavior, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE-ID: Q95235
   TITLE     : ERR: "Feature Not Available" When LIST FILES Used in .EXE
               File

   ARTICLE-ID: Q121211
   TITLE     : PRB: EVALUATE() and Exponentiation Cause Error Message


Additional reference words: FoxDos 2.60 buglist2.60 fixlist2.60a
KBCategory: kbprg kbfixlist kbbuglist kberrmsg
KBSubcategory:
Solution 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: October 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.