------------------------------------------------------------------------
                  ANSWERS TO COMMONLY ASKED QUESTIONS
------------------------------------------------------------------------
TABLE OF CONTENTS

1   How do I obtain product support?

2   When I start FoxPak, an an error 1195 occurs with the message "Object
    file '<file>' is the wrong version."  What's wrong?

3   When I open the library file, an error number 1711 occurs with the
    message "API library revision mismatch."  What's wrong?

4   When I open the library file, an error number 1709 occurs with the
    message "Cannot load 16-bit API interface."  What's wrong?

5   An error number 1001 occurs with the message "Feature not available."
    What's wrong?

6   When I call ZERRSYS() or ZERRLOG(), the screen clears.  What's wrong?

7   When I press F1 for help on a FoxPro dialog, FoxPak Help is displayed
    instead.  What's wrong?

------------------------------------------------------------------------
Question 1

How do I obtain product support?

Answer 1

If you have a problem or question, first consult this Q&A.TXT file or the
online help facility.  If you cannot find the answer, contact product
support in one of the following ways.

-   Send e-mail via CompuServe: 70401,2012 or Internet:
    70401.2012@compuserve.com

-   Call (206) 285-8116 at any time.

-   Fax your question or problem to us at (206) 644-5383, available 24
    hours a day.

-   Send mail to Jigsoft Product Support, P.O. Box 52706, Bellevue, WA
    98015-2706.

------------------------------------------------------------------------
Question 2

When I start FoxPak, an an error 1195 occurs with the message "Object file
'<file>' is the wrong version."  What's wrong?

Answer 2

The version of FoxPro you are using is incompatible with FoxPak.  This
version of FoxPak supports FoxPro 2.5/2.6 for DOS and Windows.

------------------------------------------------------------------------
Question 3

When I open the library file, an error number 1711 occurs with the message
"API library revision mismatch."  What's wrong?

Answer 3

See Answer 2.

------------------------------------------------------------------------
Question 4

When I open the library file, an error number 1709 occurs with the message
"Cannot load 16-bit API interface."  What's wrong?

Answer 4

If you are using the Extended version of FoxPro for DOS and your FoxPro
configuration file (CONFIG.FP) contains DOSMEM=ON, a library file cannot be
opened.  This is because all DOS memory is used by FoxPro, leaving no
available memory for the library file.

Set DOSMEM=OFF or specify the amount of DOS memory you want to reserve for
opening library files.  For more information, see Configuring FoxPro in
FoxPro's online help facility.

Note that the DOSMEM setting is ignored if you run FoxPro for DOS from
within Windows.

------------------------------------------------------------------------
Question 5

An error number 1001 occurs with the message "Feature not available."
What's wrong?

Answer 5

This is an erroneous FoxPro message that occurs when available memory is
insufficient.  Even if you free memory, this message may recur until you
restart FoxPro.

------------------------------------------------------------------------
Question 6

When I call ZERRSYS() or ZERRLOG(), the screen clears.  What's wrong?

Answer 6

This is caused by an anomaly in FoxPro 2.5 for Windows.  If text is
displayed on the last three rows of the screen, the LIST ... NOCONSOLE
command clears the screen.  Solutions include saving and restoring the
screen (with SAVE SCREEN and RESTORE SCREEN) and upgrading to FoxPro 2.6.

------------------------------------------------------------------------
Question 7

When I press F1 for help on a FoxPro dialog, FoxPak Help is displayed
instead.  What's wrong?

Answer 7

When you press F1 on a FoxPro dialog, FoxPro always opens the Help window
for the current help file.  To switch to FoxPro help, issue SET HELP TO in
the Command window.