Beruflich Dokumente
Kultur Dokumente
Description
----------New Features in FoxPro 2.6
Installation Notes
New and Enhanced Commands and Functions
Notes about the Catalog Manager
Notes about Wizards
Macro Key Support in FoxPro 2.6
FoxPro and Other Applications
International and Cross-Platform Recommendations
Installation Questions and Answers
Product Support Questions and Answers
---------------------------------------------------------===================================
Part 1: New Features in FoxPro 2.6
===================================
Microsoft FoxPro version 2.6 includes the following
new features:
* A Catalog Manager interface that provides convenient
access to database files and functions, and enables you
to convert dBASE(R) files easily.
* A collection of wizards that simplify common database
tasks.
* Language additions that provide dBASE IV(R) language
compatibility.
FoxPro version 2.6 includes existing print
documentation from version 2.5, as well as significant
updates to the Help file that describe new 2.6
functionality. For more information, see the What's New
Since FoxPro 2.5 Help topic.
Important: The FoxPro Catalog Manager is not available in
the 16-bit Standard version of FoxPro. To convert dBASE III(R)
and dBASE IV files in the 16-bit Standard version, select
Convert dBASE files... from the Run menu. For more help
converting files, press F1 while in this dialog.
----------------------------------------------------------
===========================
Part 2: Installation Notes
===========================
There are three types of installation for FoxPro for
MS-DOS: Normal Installation, Administrative Installation
and Workstation Installation. Instructions for Normal
Installation are in the FoxPro Installation and
Configuration manual. For information about Administrative
and Workstation Installation, see INSTALL.TXT on FoxPro
for MS-DOS Disk 1.
Installing FoxPro on the Microsoft Windows NT(TM)
operating system
------------------------------------------------FoxPro for MS-DOS cannot install in an MS-DOS window within
Microsoft Windows NT. To install FoxPro for MS-DOS, you must
be able to boot to a separate MS-DOS partition.
---------------------------------------------------------=================================================
Part 3: New and Enhanced Commands and Functions
=================================================
Several commands and functions are new to FoxPro 2.6,
and some have been enhanced to provide additional
compatibility with dBASE IV(R). For additional information
about these commands and functions, see the New and Enhanced
Commands and Functions Help topic.
New/Enhanced Commands
--------------------ON BAR
ON EXIT BAR
ON EXIT MENU
ON EXIT PAD
ON EXIT POPUP
ON MENU
ON MOUSE
ON PAD
ON POPUP
SET CPCOMPILE
SET CPDIALOG
SET COLLATE
SET DIRECTORY
SET FIELDS
SET FORMAT
SET KEY
SET NOCPTRANS
SET VIEW
New/Enhanced Functions
---------------------BARCOUNT( )
BARPROMPT( )
BLANK
CPCURRENT()
CPDBF()
CPCONVERT()
DESCENDING( )
FLDCOUNT( )
FOR( )
FTIME( )
HOME( )
ID( )
IDXCOLLATE()
ISBLANK( )
ISMOUSE( )
KEYMATCH( )
MEMORY(0)
MEMORY(1)
MEMORY(2)
MEMORY(3)
MEMORY(4)
MEMORY(5)
MEMORY(6)
MEMORY(7)
PADPROMPT( )
PCOUNT( )
PRTINFO( )
RUN( )
SET("ATTRIBUTES")
SET("DIRECTORY")
SET("DISPLAY")
SET("LIBRARY")
SET MBLOCK
SET("MBLOCK")
SYS(1037)
TAG( )
TAGCOUNT( )
TAGNO( )
UNIQUE( )
WINDOW( )
New/Enhanced System Memory Variables
-----------------------------------_ASSIST
_SHELL
---------------------------------------------------------========================================
Part 4: Notes about the Catalog Manager
========================================
Reserved Names in the Catalog Manager
------------------------------------Like any other FoxPro application, the Catalog Manager calls
and runs procedures and programs whose names may interfere
with other user-defined procedures and programs.
When you execute a program or procedure, FoxPro searches for
the program or procedure in a specific order. This order
includes the current file as well as programs that were
executed prior to the current one, including the Catalog
Manager itself.
Below is a list of procedure and program names that can cause
Question 1
Why does the FoxPro installation sometimes stop before
allowing the installation of optional components?
Answer 1
Sometimes in low memory conditions the installation program
is unable to determine whether to run the Standard
(FOXPRO.EXE) or the 32-bit Extended (FOXPROX.EXE) version
to complete the installation. If you're installing from
within Windows, you can exit Windows to make more memory
available. If you have any TSR programs residing in memory,
removing them from memory may free additional memory. For
information on installing optional components after you have
installed FoxPro, see Question 2 in this section.
---------------------------------------------------------Question 2
How do I install additional files that I didn't specify
during installation?
Answer 2
below 250.
The FILES statement should always be at least 10 more than
the greatest number of files that you will have open at
one time. We recommend that you set FILES to 40 or greater.
---------------------------------------------------------Question 5
Can I run the FoxPro 32-bit Extended version in Enhanced
Mode Windows or with EMM386 with the NOEMS option?
Answer 5
Yes. FoxPro works with DPMI-compliant memory managers,
such as Microsoft Windows and EMM386. If you use a DPMI
memory manager, you can control the physical memory that
FoxPro uses by specifying the MEMLIMIT option in your
CONFIG.FP file. For more information on the MEMLIMIT option,
refer to the Update manual and to "Changes to Documentation
Since Printing" in Help.
---------------------------------------------------------Question 6
What factors influence FoxPro startup speed?
Answer 6
The time required to load and start FoxPro relates to the
physical size of FoxPro, the length of the path in effect,
the number of items FoxPro has to locate at startup, and
other factors. You can control many of these items.
For a complete discussion of this issue, refer to
"Optimizing Your System" in the Installation and
Configuration manual.
---------------------------------------------------------Question 7
I'm receiving the error message "Too many files open."
How can I correct this problem?
Answer 7
If you receive this error message, use one or more of the
following strategies:
* Increase the FILES setting in the CONFIG.SYS file.
* If you are using a Novell network, increase the FILE
HANDLES setting in the SHELL.CFG file.
* If you are using the MS-DOS SHARE program, increase the
number of files and locks. For example, you could use
SHARE /F: 4096 /L:500 in the CONFIG.SYS file.
---------------------------------------------------------Question 8
The Standard version of FoxPro for MS-DOS runs
correctly on my computer, but when I load the 32-bit
Answer 11
The MS-DOS SHARE program is the most common cause of this
problem. Current workarounds include marking the FoxPro
FOXPRO.EXE and FOXPROX.EXE files read only, running under
Windows for Workgroups, or running a copy of FoxPro from
a network location.
---------------------------------------------------------Question 12
I get Cannot Create <Path>\FOXPRO.EXE" Error
During Installation. How can I correct this problem?
Answer 12
One possible cause is that FOXPRO.EXE or FOXPROX.EXE already
exists in that directory and it is marked read-only.
For the Setup program to be able to perform a successful
install, the .EXE file must be either renamed or marked as
read/write. The command ATTRIB -R <path>\FOXPRO.EXE will
remove the Read-Only attribute from the file.
---------------------------------------------------------Question 13
What are the minimum files required to run FoxPro?
Answer 13
Not all files placed on the hard disk during installation
of FoxPro are absolutely required for operation of the
product. FoxPro for MS-DOS can be started with only two
files: FOXPRO.EXE and FOXPRO.OVL. For the extended (32 bit)
version, these two files can be replaced by only one,
FOXPROX.EXE.
The minimum files needed to run FoxPro, use the menu and
screen generators, and set printer drivers are listed below.
NOTE: Upon startup, FoxPro will create FOXUSER.DBF and
FOXUSER.FPT files, and upon screen or menu generation, it
will create the appropriate .FXP files.
Versions 2.6 (MS-DOS)
-----------------------------Filename
Bytes
Comments
-----------------------------------------------------DRIVER2.PLB
FOXSWAP.COM
GENMENU.PRG
GENPD.APP
GENSCRN.PRG
GENXTAB.PRG
PSAPI.PLB
14029
5971
57109
374351
292613
29246
24451
FOXPRO.EXE
FOXPRO.OVL
411599
1424976
--------------------------------------------------------Question 14
A "CRC Error" Occurs During Setup.
How can I correct this error?
Answer 14
When reading a disk, MS-DOS performs a cyclical redundancy
check (CRC) to verify disk sectors. The CRC is a
sophisticated parity check of the data in each sector and
will detect most data errors, such as lost or scrambled
bits.
To determine if there is a problem with the disks:
1. Attempt the installation a second time.
2. Install on a "clean" (minimal) configuration.
3. Install on another machine to verify there is not a
hardware problem.
4. Copy the floppy disks to a temporary directory on the
hard disk and run the Setup program from this temporary
directory.
If the installation still fails, call Microsoft Product
Support Services for assistance.
--------------------------------------------------------Question 15
The following error occurs File 'ADDUSER.APP' Does Not
Exist" Running INSTALL /N. How can I correct this?
Answer 15
The INSTALL /N command was not issued from the directory
containing the Administrative Installation (INSTALL /A) of
FoxPro.
After a Workstation Installation completes the Basic
portion of its installation, it calls the FoxPro program
ADDUSER.APP to configure the workstation for the network
environment. In order for FoxPro to load and run
ADDDUSER.APP, the current directory must be the
Administrative Installation directory.
Even if the Administrative Installation directory is on
the MS-DOS search path, allowing FoxPro itself to start,
because ADDUSER.APP is not an MS-DOS executable program
(.COM or .EXE), it cannot be located on the path, thus
causing the error message.
RESOLUTION
Answer 1
In the United States, call 800-426-9400.
---------------------------------------------------------Question 2
Where can I go for additional FoxPro product support?
Answer 2
Call *Microsoft FastTips* to hear recorded responses to
common questions about Microsoft FoxPro. You can also
order technical notes that will be sent to your fax
machine. FastTips is available seven days a week, 24
hours a day. For assistance with FoxPro, dial 206-635-7190.
Use the *Microsoft Forums* on CompuServe. You can discuss
current support and design issues with other developers and
download sample files from the libraries. For an
introductory CompuServe membership kit specifically for
Microsoft users, call CompuServe at 800-848-8199 and ask
for operator 170. If you are already a CompuServe member,
type GO MICROSOFT at any ! prompt. For specific FoxPro
information, type GO FOXFORUM, or GO FOXUSER.
Use the *Microsoft Download Service* to access technical
notes and supplementary files covering common Microsoft
product support issues. This service is available via
modem 24 hours a day, seven days a week at 206-936-6735.
Call *Microsoft Product Support Services* between 6 a.m.
and 6 p.m. Pacific time, Monday through Friday. For
assistance with Microsoft Fox products for MS-DOS or for
Windows, call 206-635-7191. For assistance with Microsoft
Fox products for the Macintosh, call 206-635-7192.
Microsoft support services are subject to Microsoft prices,
terms, and conditions that are in place at the time the
service is used.
---------------------------------------------------------Question 3
If I call for support or post a message on the FoxForum,
what information should I include?
Answer 3
When you call, you should be at your computer and have the
appropriate product documentation at hand. Be prepared to
give the following information:
* The version number and platform of the Microsoft Fox
product you are using.
This can be obtained by typing ?VERSION(1) in the Command
window for FoxPro.
* The type of hardware you are using, including network
hardware if applicable; and the operating environment