Contents of 2.6 DKREADME.TXT in the FOXPROW Directory

Last reviewed: April 30, 1996
Article ID: Q117592
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6

SUMMARY

Below is the complete FoxPro for Windows DKREADME.TXT file found in the main FoxPro directory (usually FOXPROW).

MORE INFORMATION

DKREADME.TXT ********************************************************** Microsoft(R) FoxPro(R) Version 2.6 Professional Edition

Distribution Kit for Windows(TM)

 (C)1994 Microsoft Corporation. All Rights Reserved.
**********************************************************

CONTENTS

Part Description ---- -----------

 1     Installation
 2     Knowledge Base Articles
 3     The Help Compiler and Microsoft Word for Windows
 4     Changes to Distribution Kit User's Guide Since
       Printing
 5     Answers to Commonly Asked Questions

Part 1: Installation

Installing the Professional Edition of FoxPro Version 2.6

The Professional Edition of FoxPro version 2.6 includes the following kits:

Distribution Kit Connectivity Kit Library Construction Kit WorkGroup Extensions (FoxPro for Windows only)

To install the Professional Edition of FoxPro, first install the main FoxPro product, then follow the installation instructions included with each individual kit. The order in which the kits are installed does not matter.

FoxPro version 2.6 now includes the FoxPro Wizards, located in the WIZARDS subdirectory. The FoxPro Wizards and CATALOG.APP should not be distributed with your applications.

Part 2: Knowledge Base Articles

If you installed the Knowledge Base articles, you can view them by running the application KBVIEW.APP. These articles contain useful information about a variety of FoxPro topics.

Part 3: The Help Compiler and Microsoft Word for Windows

The Help Compiler version 3.10.504 shipped with the Distribution Kit, does not support Word for Windows version 6.0 RTF files. You can obtain a version of the Help Compiler that supports Word for Windows

version 6.0 RTF through the Microsoft Developer's Network.

Part 4: Changes to Distribution Kit User's Guide Since Printing

In the Distribution Kit User's Guide, references to FoxPro version 2.5 should be read as references to FoxPro version 2.6.

In the documentation, the FoxPro for Windows Distribution Kit support file is called FOXW2500.ESL. The support file name should be FOXW2600.ESL.

Chapter 1, page 5: Installation

This section incorrectly states that FOXW2500.ESL (FOXW2600.ESL) and DKREADME.TXT are installed in the Distribution Kit directory. These files are actually installed in your FoxPro for Windows directory.

Chapter 2, page 12: Including FoxPro for MS-DOS Printer Drivers

You should also include DRIVER2.FLL as a file if your application requires FoxPro for MS-DOS printer drivers.

Chapter 2, page 13: Modifying the Main FoxPro Window TITLE, a new FoxPro for Windows configuration file (CONFIG.FPW) item, was not documented in this section.

If you select Close from your application's Control Menu or Exit from the File menu, a message containing the text in your application's title bar is displayed.

Include the TITLE configuration item to specify the message displayed when you select either of these two options. The title bar text is overridden by the text you specify with the TITLE configuration item.

For example, the message "Exit MyApp" is displayed when the following line is place in CONFIG.FPW: TITLE = MyApp

Chapter 3, page 17: Adding an Icon to your .EXE File

The warning states that you cannot use the Program Item Properties dialog in the Windows Program Manager to add or change the icon for an .EXE file created with the FoxPro for Windows Distribution Kit. This is not correct. You can use the Program Item Properties dialog in the Windows Program Manager to manipulate the icon for a .EXE created with the Distribution Kit.

Part 5: Answers to Commonly Asked Questions

Overview of Questions

1 Where does my application's executable (.EXE) file look for

    FOXW2600.ESL?

2 If my application uses the RUN command to execute external MS-DOS
    programs, where should I put FOXRUN.PIF?

3 How do I pass parameters to my application's executable (.EXE) file?

4 My application uses FoxFont. Where do I put the FoxFont

    file FOXFONT.FON?

5 Our organization includes several FoxPro developers. Does each
    developer need an individual copy of the Distribution Kit?

6 What type of applications (single or multiuser) can be built
    with the Distribution Kit?

7 A two-part question about the sale of an application via a reseller.

8 Should I distribute FOXPRO.INT with my application?

Questions and Answers

Question 1

Where does my application's executable (.EXE) file look for FOXW2600.ESL?

Answer 1

The executable file looks for FOXW2600.ESL, the FoxPro for Windows Support Library, in the following locations in this order:

  1. In the directory from which the .EXE is run.

  2. In the current working directory.

  3. Along the MS-DOS path.

Question 2

If my application uses the RUN command to execute external MS-DOS programs, where should I put FOXRUN.PIF?

Answer 2

Place FOXRUN.PIF in the same directory as the FOXW2500.ESL file. This is usually the root directory of the directory structure containing the files you want on your distribution diskettes.

Question 3

How do I pass parameters to my application's executable file (.EXE)?

Answer 3

The first line of your application's main program must be a PARAMETERS statement to accept the parameters you pass. For example, the following PARAMETERS statement can be used to accept two parameters:

PARAMETERS mparam1, mparam2

You can specify the parameters that are passed to your application's .EXE file when you use the SetupWizard to create your setup routine. Specify the parameters in the screen where the SetupWizard asks you for the name of your application. If you specify more than one parameter, separate the parameters with a space. If a parameter contains an embedded space, place double quotation marks (" ") around the parameter.

You can also specify parameters to pass to the application's .EXE file by selecting the application's icon and choosing Properties... from the Program Manager File menu. Enter the parameters to pass to the .EXE file in the Command Line text box.

Question 4

My application uses FoxFont. Where do I put the FoxFont file FOXFONT.FON?

Answer 4

Place FOXFONT.FON in the same directory as the FOXW2600.ESL file. This is usually the root directory of the directory structure containing the files you want on your distribution disks.

Question 5

Our organization includes several FoxPro developers. Does each developer need an individual copy of the Distribution Kit?

Answer 5

Your organization must own one licensed copy of the Distribution Kit per developer, for each developer creating applications for distribution. If five developers in your organization create applications for istribution, you must own five licensed copies of the Distribution Kit.

Question 6

What type of applications (single or multiuser) can be built with the Distribution Kit?

Answer 6

You can build all types of applications (single and multiuser) with the FoxPro version 2.6 for Windows Distribution Kit. While the FoxPro version 2.0 Distribution Kit required separate license agreements for single user, multiuser, and so on, the development version of FoxPro version 2.6 no longer makes these distinctions. However, as mentioned in the previous answer, in order to be legally correct, you must own one licensed copy of the FoxPro version 2.6 for Windows Distribution Kit for each developer creating FoxPro version 2.6 applications for distribution.

Question 7

I have a question regarding the legal requirements for reselling applications developed with FoxPro. Let's say that, as a FoxPro developer, I write a program for Client A. I compile the program as a compact .EXE file and give the application to Client A, together with the FOXW2600.ESL support library file with which to run the application. Client A owns the application and the copyright. Client A then sells the application commercially to many other people.

A) Does Client A also have to purchase the FoxPro Distribution Kit,

   even though Client A will never use the Distribution Kit themselves?

B) Does Client A have to purchase the FoxPro version 2.6 development version?

Answer 7

A) No, Client A does not need to purchase the Distribution Kit. Only

   the developer who uses the Distribution Kit to build the original
   .EXE file must own a licensed copy of the Distribution Kit.

B) Client A does not have to purchase FoxPro version 2.6, because the
   client is not building their own .EXE file; Client A is just a reseller.
   Client A must distribute the application in its original form, however,
   and cannot remove the runtime files to include it with another
   application.

Question 8

Should I distribute FOXPRO.INT with my application?

Answer 8

We recommend that you include FOXPRO.INT, the FoxPro international file that provides additional collation sequence and code page support, with your distributed application. You must include FOXPRO.INT with your application if it uses a collation sequence other than MACHINE or is run on multiple FoxPro platforms.

Place FOXPRO.INT in the root directory of the directory structure containing the files you want on your distribution disks.

                     ===================
                     END OF DKREADME.TXT
                     ===================


Additional reference words: FoxWin 2.60 readme q&a
KBCategory: kbreadme kbprg
KBSubcategory: FxotherReadme


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: April 30, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.