TXT
**********************************************************
Microsoft(R) FoxPro(R) Version 2.6 Professional Edition
Distribution Kit for MS-DOS(R)
(C)1994 Microsoft Corporation. All Rights Reserved.
**********************************************************
=========
CONTENTS
=========
Part
---1
2
3
Description
----------Installation
Knowledge Base Articles
Changes to Distribution Kit User's Guide Since
Printing
4
Answers to Commonly Asked Questions
5
Error Messages
---------------------------------------------------------=====================
Part 1: Installation
=====================
Installing the Professional Edition of FoxPro 2.6
------------------------------------------------The Professional Edition of FoxPro 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: Changes to Distribution Kit User's Guide
Since Printing
=================================================
In the Distribution Kit User's Guide, references to FoxPro
2.5 should be read as references to FoxPro 2.6.
---------------------------------------------------------Chapter 1, page 2: The first bulleted item should read:
"The Distribution Kit files, in both 5.25-inch and
3.5-inch disk formats."
---------------------------------------------------------Chapter 2, page 10, under "Available Runtime Menus and Menu
Options," the File menu item should read:
File menu: Close, Save, Save As and Revert
---------------------------------------------------------Chapter 2, page 11, under "Features Not Available in
Distributed Applications," add the following section below
the "Menus" section:
Menu Pads
The following FoxPro menu pads aren't available in the
applications you distribute.
SYSTEM Menu: Macros..., Filer
FILE Menu: New..., Open..., Printer setup...,
Print..., Quit
WINDOW Menu: Color..., Command, Debug, Trace, View
---------------------------------------------------------The files with extensions .ESL or .ESO have been renamed for
the new version. For example:
FOXPRO.ESL is now FOXD2600.ESL
FOXPRO.ESO is now FOXD2600.ESO
FOXPROX.ESL is now FOXDX260.ESL
The new file names impact the following pages in the
Distribution Kit User's Guide:
Chapter 1, page 5, the Distribution Kit Files table.
Chapter 3, page 22, change the last sentence to read:
"The .EXE Support Library consists of three files:
FOXD2600.ESL, the standard .EXE Support Library
FOXD2600.ESO, and the 32-bit Extended .EXE Support
Library FOXDX260.ESL."
Chapter 5, page 32, the table called Files Required on
Distribution Disks Based on Type of Application has
these changes:
In the "You must also distribute these files" column,
substitute the .ESL and .ESO file names with the new
File names.
----------------------------------------------------------
Question 6
I have created an application that does not allow me to
edit my table/.DBF files. How can I correct this problem?
Answer 6
Mark your table/.DBF as excluded in the project, then
rebuild your application. You must distribute these files
to your end users. Including the table/.DBF in the project
automatically makes these files read only.
---------------------------------------------------------Question 8
How do you instruct an MS-DOS .FXP, .APP or compact .EXE
file to run in extended mode from within Windows?
Answer 8
An .FXP, .APP or .EXE file will run in standard mode when
run from within Windows, even though there is enough
memory for the extended mode Support Library to run. To
force use of the Extended Support Library from within
Windows, you can use the +X loader switch to launch your
application.
---------------------------------------------------------=======================
Part 5: Error Messages
=======================
Message: "Feature Not Available"
Question 1
My executable file runs correctly in the development
version of FoxPro, but I receive the error message
"Feature Not Available" when running the stand-alone
application. How can I correct this problem?
Answer 1.1
You will get the "Feature not available" error message
when you use commands, features, and menus that require
the development version of FoxPro. Refer to the "Features
Not Available in Distributed Applications" list in the
FoxPro Distribution Kit User's Guide for a list of these
commands and functions. These commands and functions
include: BUILD APP, BUILD EXE, BUILD PROJECT, COMPILE,
FILER, CREATE/MODIFY MENU, CREATE/MODIFY QUERY,
CREATE/MODIFY SCREEN, SET VIEW ON, and SUSPEND and
features specific to the interactive development
environment such as the Trace, Debug, Command, and
View windows.
Answer 1.2
You will get the "Feature not available" error message
when using commands containing macro substitution in
pack
return
---------------------------------------------------------Message: "Dynamic memory exhausted"
Question 1
What is the cause and solution for a "Dynamic memory
exhausted" error message when compiling a stand-alone
.EXE file?
Answer 1
This error message is sent by the WATCOM linker, which
is one of the tools in the FoxPro Distribution Kit used
to create a stand-alone application. The message is
displayed when the amount of available conventional
memory is too low. The WATCOM linker (WLINK8.EXE) uses
only conventional memory.
If the CONFIG.FP file contains the DOSMEM=ON statement,
edit the file to remove the statement. If the CONFIG.FP
file does not contain a DOSMEM statement, edit the
AUTOEXEC.BAT and CONFIG.SYS files to remove unnecessary
device drivers and memory-resident applications to
maximize available conventional memory.
---------------------------------------------------------Message: "Link command failed"
Question 1
When I attempt to build an executable file, I receive the
error message "Link command failed." How can I correct
this problem?
Answer 1
If you receive this error message, check the following
items:
a. Make sure that enough conventional memory is available.
Modify the CONFIG.SYS and AUTOEXEC.BAT files to free
conventional memory.
b. Make sure that enough disk space is available.
c. Increase the number of file handles available to
Microsoft FoxPro for MS-DOS. To do this, you can
modify the FILES statement in the CONFIG.SYS file to
increase the number of available files. In the Novell
NetWare environment, modify the FILE HANDLES
statement in the SHELL.CFG file to increase the number
of available files.
d. If the AUTOEXEC.BAT file loads the SHARE utility,
increase the values specified by the /F and /L
parameters. For example: