Microsoft KB Archive/96160

= FastTips for FoxPro for MS-DOS: Creating Apps & EXEs Q&A =

ID: Q96160

The information in this article applies to:


 * Microsoft FoxPro for MS-DOS, version 2.5

Microsoft(R) Technical Support Application Note (Text File) FP0920: CREATING APPLICATIONS AND EXECUTABLES QUESTIONS & ANSWERS Revision Date: 9/93 No Disk Included The following information applies to Microsoft FoxPro(R) version 2.5 for MS-DOS(R).

| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY    | 1. Q. An application I have created does not allow me to edit my
 * ACCOMPANY THIS DOCUMENT (collectively referred to as an Application |
 * Note) IS PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND, EITHER     |
 * EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED     |
 * WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR      |
 * PURPOSE. The user assumes the entire risk as to the accuracy and   |
 * the use of this Application Note. This Application Note may be     |
 * copied and distributed subject to the following conditions: 1) All |
 * text must be copied without modification and all pages must be     |
 * included; 2) If software is included, all files on the disk(s)     |
 * must be copied without modification (the MS-DOS utility diskcopy is |
 * appropriate for this purpose); 3) All components of this           |
 * Application Note must be distributed together; and  4) This        |
 * Application Note may not be distributed for profit.                |
 * Copyright (C) 1993 Microsoft Corporation. All Rights Reserved      |
 * Microsoft, FoxPro, and MS-DOS are registered trademarks and Windows |
 * is a trademark of Microsoft Corporation.                           |
 * is a trademark of Microsoft Corporation.                           |

database files. How can I correct this problem?

A. Mark your database as &quot;excluded&quot; in the project, then rebuild your application. You must distribute these files to your end users. Including the database in the project automatically marks these files as read-only. 2. Q. Why can't I build an executable file from within my project?

The options to do so are dimmed and unavailable.

A. To build an executable file, you must purchase the Microsoft FoxPro Distribution Kit and install it in your FoxPro directory. Prior to installing the FoxPro Distribution Kit, make sure that the FoxPro files are not marked as read-only. 3. Q. When I attempt to build an executable file, I receive the error

message &quot;Link command failed.&quot; How can I correct this problem?

A. If you receive this error message, check the following items:

- Make sure that you have enough conventional memory.

- Make sure that you have enough disk space.

- Increase the number of file handles available to Microsoft FoxPro for MS-DOS. To do this, you can increase the FILES setting in the CONFIG.SYS file, or increase the FILE HANDLES setting in the SHELL.CFG file.

- Make sure that FoxPro can find your COMMAND.COM file.

- Make sure that the following files are on your search path: WLINK8.EXE, PROAPI16.EXE, and FOXSWAP.COM.

- If you are running the Extended version of FoxPro, make sure that DOSMEM=ON is not on in your CONFIG.FP file. 4. Q. My executable file runs correctly under the development

version, but I receive the error message &quot;Feature not available&quot; under the stand-alone version. How can I correct this problem?

A. First, check the &quot;Features Not Available&quot; list in the FoxPro Distribution Kit documentation. Certain features used for development are not available in the applications and executables you create. If you still encounter problems, it is      possible that you are using a macro substitution in your program. You must either eliminate the macro substitution or      include a program that issues the proper command, but is never called, in your project. Additional reference words: FoxDos 2.50 ivrfax fasttips KBCategory: kbtool kbprg kbfasttip kbappnote KBSubcategory:

Last Reviewed: December 12, 1996