# Contents of the FoxPro Ver 2.6 for UNIX readme File

ID: Q120928

The information in this article applies to:

- Microsoft FoxPro for UNIX, version 2.6

## SUMMARY

Below are the contents of the readme file installed with FoxPro version 2.6 for UNIX.

## MORE INFORMATION

    ************************************************************************
                       Release Notes for

              Microsoft(R) FoxPro(R) 2.6 for UNIX(R)

        (C)1994 Microsoft Corporation. All Rights Reserved.

    This readme provides information not contained in the FoxPro online
    Help file or print documentation, and provides corrections to both.
    Information in Help is more current than information in the print
    documentation.
    ************************************************************************

    ========
    CONTENTS
    ========

    Part   Description
    ----   -----------
      1    FoxPro version 2.6 for UNIX Notes
      2    Installation Notes
      3    Macro Key Support in FoxPro version 2.6
      4    Running on Non-SCO Systems
      5    scoterm Resources
      6    New and Enhanced Commands and Functions
      7    Question and Answers
    ------------------------------------------------------------------------

    =========================================
    Part 1: FoxPro Version 2.6 for UNIX Notes
    =========================================

    Documentation
    -------------
    FoxPro version 2.6 for UNIX documentation includes a UNIX-specific
    Installation and Configuration manual along with the books for FoxPro for
    MS-DOS. The Help file includes topics describing the new functionality
    included in FoxPro for UNIX.

    Correction
    ----------
    The Installation and Configuration manual incorrectly lists the return
    value of SYS(2010) as the null string. FoxPro for UNIX returns 255,
    which is the same value that FoxPro for Windows returns.

    New Key Sequence
    ----------------
    FoxPro includes a refresh key sequence to clear terminals when the
    screen becomes garbled (system wide messages, noise on the serial line).
    This key sequence is CTRL+].

    terminfo Entries
    ----------------
    See the file terminfo.src in your FoxPro installation directory
    (usually /usr/lib/foxpro) for information about what terminals are
    supported and how to write a new entry if you are having problems with
    your terminal.
    ------------------------------------------------------------------------

    ===========================
    Part 2: Installation Notes
    ===========================

    FoxPro is normally installed in the directory /usr/lib/foxpro by the
    installation utility custom. Instructions on how to install using
    custom can be found in the Installation and Configuration manual. If
    you do not want to install FoxPro in the default directory or if you do
    not have the custom utility, you can install FoxPro using the shell
    script extract located on the first installation disk.

    To use the script extract, follow these steps:

    1  Change your current directory to the directory you wish to install
       in (the default is /usr/lib/foxpro). For example, type the
       following at the system prompt and press Enter:

           cd /other/FoxPro

    2  If your 3.5-inch drive is your A: drive, to copy the extract script
       off the installation disk type the following at the system prompt and
       press Enter:

           tar xvf /dev/install ./tmp/extract

       If your 3.5-inch drive is your B: drive, use /dev/install1:

           tar xvf /dev/install1 ./tmp/extract

    3  Type one of the following to run the extract script:

       For drive A:  ./tmp/extract /dev/install

       -Or-

       For drive B:  ./tmp/extract /dev/install1

    4  Follow the system prompts.

    Note that some systems may use device names other than /dev/install and
    /dev/install1. If you get an extraction error, consult your system
    documentation for the name of your floppy device.

    If you have the directory /etc/perms, a permissions file is added to
    it. This file contains the new location of the FoxPro files so that the
    custom utility will work as expected when removing FoxPro.
    ------------------------------------------------------------------------

    ===============================================
    Part 3: Macro Key Support in FoxPro Version 2.6
    ===============================================

    In FoxPro version 2.6, the key combinations ALT+1 to ALT+9 cannot be used
    to define macros because these sequences are used by the UNIX operating
    system to switch console multiscreens. For a list of key combinations
    that are supported see the ON KEY LABEL topic in Help.
    ------------------------------------------------------------------------
    ==================================
    Part 4: Running on Non-SCO Systems
    ==================================

    Some FoxPro for UNIX features are not completely supported on platforms
    other than SCO UNIX. These features include direct video memory
    writes, the SCO event queue management system, scancode support on
    terminals, and compression technology. Below is a description of how
    to work around these features. For more information on the command
    line switches described see the "Customizing FoxPro" chapter in the
    Installation and Configuration manual.

    Direct Video Memory Writes
    --------------------------
    On some non-SCO systems, accessing the console video memory directly
    results in the loss of multiple-screen functionality. To disable direct
    video memory writes, include the -o switch on the command line when
    starting FoxPro.

    SCO Event Queue Management
    --------------------------
    Some systems either do not support the SCO event queue system, or do so
    incorrectly. If you are having trouble accessing the keyboard, include
    the -e switch on the command line when starting FoxPro to disable the
    event queue.

    Scan Code Support
    -----------------
    Most non-SCO systems do not support scan codes over a serial line and
    some have trouble even on the console. To disable scan code support
    add the -i switch on the command line when starting FoxPro.

    Compression Utility
    -------------------
    Most of the FoxPro installation files are compressed. SCO supports a
    version of tar that automatically uncompresses the compressed files.
    If you aren't running SCO UNIX 3.2.2, XENIX 2.3.4, or a later version
    of these products, you won't have the correct version of tar. When
    this happens, the installation scripts attempt to decompress with the
    uncompress utility. If both tar and the uncompress utility are not
    present, you will not be able to install FoxPro. For more information
    about uncompress utilities supported by your system, see your
    system documentation.
    ------------------------------------------------------------------------

    ========================================
    Part 5: scoterm Resources
    ========================================

    The resource file that SCO ships for scoterm (/usr/lib/X11/app-
    defaults/ScoTerm) may not provide all of the resources necessary to run
    FoxPro effectively in a scoterm window. scoterm will not run in scancode
    mode unless the *keyboard resource is set to a value (for example, us).
    Also, the default colors need to be set up to match the console's colors.

    See the file goodies/scoterm.res for the correct resources.
    ------------------------------------------------------------------------

    ===============================================
    Part 6: New and Enhanced Commands and Functions
    ===============================================

    Several commands and functions are new to FoxPro version 2.6, and some have
    been enhanced to provide additional compatibility with dBASE(R) IV. For
    additional information about these commands and functions, see the
    following topics in the Help file: Doc Changes Since Printing, dBASE
    Compatibility Issues, International/X-Platform, or the name of the
    specific command or function.

    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 COLLATE
    SET CPCOMPILE
    SET CPDIALOG
    SET DIRECTORY
    SET FIELDS
    SET FORMAT
    SET KEY
    SET NOCPTRANS
    SET VIEW

    New/Enhanced Functions
    ----------------------
    BARCOUNT( )
    BARPROMPT( )
    BLANK
    CPCONVERT()
    CPCURRENT()
    CPDBF()
    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 7: Question and Answers
    =========================================

    Topic   Description
    -----   -----------
      1     Installation Issues
      2     Multiuser Issues
      3     Converting from FoxPro for MS-DOS, Windows, or Macintosh
      4     Printing Issues
      5     Screens
      6     Importing Data
      7     BROWSE Command
      8     Creating Applications
    ------------------------------------------------------------------------

    Topic 1: Installation Issues
    =============================

    Overview of Questions
    ---------------------
    1  I receive the error message "File is in use by another" when I try
       to open a file. No one else has the file open. How can I solve
       this?
    2  I receive the error message "NOTICE: File table overflow" or
       "No file". How can I correct this?
    3  The message "Position is off the screen" appears. How can I correct
       this problem?
    4  Certain keystrokes do not work as intended or do not exist on my
       keyboard. How can I fix this?
    5  My terminal locks up or freezes when I use a control keystroke
       combination.
    6  One or more characters seem to disappear for no apparent reason.
       How can I correct this problem?
    7  Pressing the left arrow key deletes characters. How can I stop this
       from happening?
    8  I cannot access a file for which I should have permission. How can
       I correct this?
    9  I get the message "File too large" or files can not be written
       beyond a certain size. How can I correct this?
    ------------------------------------------------------------------------

    Question 1

    I receive the error message "File is in use by another" when I try to
    open a file. No one else has the file open. How can I solve this?

    Answer 1

    The UNIX kernel grants a limited number of file locks to all
    applications. The number of locks available can be selected by running
    the configure command in /etc/conf/cf.d.
    ------------------------------------------------------------------------

    Question 2

    I receive the error message "NOTICE: File table overflow" or "No file".
    How can I correct this?

    Answer 2

    The UNIX kernel grants a limited number of open files to each
    application. The number of open files available can be selected by
    running the configure command in /etc/conf/cf.d.
    ------------------------------------------------------------------------

    Question 3

    The message "Position is off the screen" appears. How can I correct
    this problem?

    Answer 3

    Your terminal is trying to access a line that is off the screen.
    FoxPro expects there to be at least 25 lines. If possible, your
    terminal should be configured to be at least 25 lines.
    ------------------------------------------------------------------------

    Question 4

    Certain keystrokes do not work as intended or do not exist on my
    keyboard. How can I fix this?

    Answer 4

    Refer to "Special Terminal Considerations for UNIX" in Chapter 2 of the
    Installation and Configuration manual or "Keystrokes for Terminals" in
    the Help file.
    ------------------------------------------------------------------------

    Question 5

    My terminal locks up or freezes when I use a control keystroke
    combination.

    Answer 5

    Some terminals have key press sequences that lock the terminal. In
    most cases you can choose an alternate key sequence. For more
    information about key sequences, refer to "Special Terminal
    Considerations for UNIX" in Chapter 2 of the Installation and
    Configuration manual or "Keystrokes for Terminals" in the Help file.
    ------------------------------------------------------------------------

    Question 6

    One or more characters seem to disappear for no apparent reason. How
    can I correct this problem?

    Answer 6

    Your terminal may be experiencing standout glitch. Some terminals need
    to use one character position on the screen when changing in and out of
    reverse video. You may be able to turn off this attribute byte or
    choose another emulation that does not need it. See your system
    documentation for more information.
    ------------------------------------------------------------------------

    Question 7

    Pressing the left arrow key deletes characters. How can I stop this
    from happening?

    Answer 7

    Your terminal may emit the same sequence for the left arrow as it does
    for the backspace key. Refer to your system documentation to find out
    if your terminal has an emulation that generates different sequences
    for the arrow keys. You may also define the "kbs" string in your
    terminfo entry to something other than CTRL-H (such as CTRL-B).

    ------------------------------------------------------------------------

    Question 8

    I cannot access a file for which I should have permission. How can I
    correct this?

    Answer 8

    To determine the file's permission, type the following at the UNIX
    prompt:

           ls -l <filename>

    If you own the file and it needs to be made writable, type:

           chmod +w <filename>

    If you do not own the file and need to change permissions, contact the
    owner of the file.
    ------------------------------------------------------------------------

    Question 9

    I get the message "File too large" or files can not be written beyond a
    certain size. How can I correct this?

    Answer 9

    UNIX has a configuration option named ulimit that can be set to limit a
    file's size. Each process can set its own ulimit, but it must be less
    than or equal to the system's ulimit. The system wide ulimit can be
    set by running the configure command in /etc/conf/cf.d.
    ------------------------------------------------------------------------

    Topic 2: Multiuser Issues
    =========================

    Overview of Questions
    ---------------------
    1  When a second user loads Microsoft FoxPro for UNIX, the user
       receives the error message "File in use by another."  How can I
       correct this problem?
    2  Where does FoxPro create temporary files?
    3  I'd like to refer to a directory with a single drive letter. Is
       this possible?
    ------------------------------------------------------------------------

    Question 1

    When a second user loads Microsoft FoxPro for UNIX, the user receives
    the error message "File in use by another." How can I correct this
    problem?

    Answer 1

    Several solutions exist. Verify that the user has read permission to
    all necessary FoxPro files, including foxuser.dbf, foxuser.fpt, and
    config.fpu (where applicable). Also, all users must have execute
    permission for foxpro.pr. See your system administrator to change
    permissions.

    Check the permissions on the resource file in FoxPro called foxuser.dbf.
    This file stores information about windows, color sets, and other FoxPro
    objects. The foxuser database can be used by multiple users by removing
    write permissions and granting read permissions.

    If you receive the "File in use by another" error message when you try
    to open a database file, make sure that all users have the SET EXCLUSIVE
    setting OFF.
    ------------------------------------------------------------------------

    Question 2

    Where does FoxPro create temporary files?

    Answer 2

    FoxPro creates temporary files in the /tmp directory unless you
    specifically designate an different location. For more information, see
    Chapter 5, "Optimizing Your UNIX System," in the Installation and
    Configuration manual.
    ------------------------------------------------------------------------

    Question 3

    I'd like to refer to a directory with a single drive letter. Is this
    possible?

    Answer 3

    Yes, you can use the SET VOLUME command to do this. For example, to
    associate the /usr/main directory to C, type SET VOLUME C TO /usr/main
    at the system prompt, or type VOLUME C = /usr/main in config.fpu.
    NOTE: The volume specified in the SET VOLUME command must exist on the
    computer system.
    ------------------------------------------------------------------------

    Topic 3: Converting from FoxPro for MS-DOS, Windows, or Macintosh
    =================================================================

    Overview of questions
    ---------------------
    1  Are my existing FoxPro version 2.6 for MS-DOS, Windows and Macintosh
       screens and reports compatible with FoxPro version 2.6 for UNIX?
    2  Can I use my existing library files in FoxPro version 2.6 for UNIX?
    3  Are my existing programs compiled under FoxPro version 2.6 for MS-DOS
       compatible with FoxPro version 2.6 for UNIX?
    4  Can I distribute my FoxPro version 2.6 for UNIX applications?
    ------------------------------------------------------------------------

    Question 1

    Are my existing FoxPro for MS-DOS, Windows and Macintosh 2.6 screens and
    reports compatible with FoxPro version 2.6 for UNIX?

    Answer 1

    The structures of the databases created by the power tools from other
    platforms are compatible with FoxPro version 2.6 for UNIX. When you first
    open screen and report files created on other platforms, FoxPro asks if you
    want to transport them to FoxPro version 2.6 for UNIX format. For more
    information about specific FoxPro version 2.6 file formats, see the
    Update manual.
    ------------------------------------------------------------------------

    Question 2

    Can I use my existing library files in FoxPro version 2.6 for UNIX?

    Answer 2

    Library files cannot be used with FoxPro for UNIX. FoxPro for UNIX has
    no Library Construction Kit and does not support LOAD or CALL functions.
    ------------------------------------------------------------------------

    Question 3

    Are my existing programs compiled under FoxPro version 2.6 for MS-DOS
    compatible with FoxPro version 2.6 for UNIX?

    Answer 3

    Programs compiled under FoxPro version 2.6 for MS-DOS, such as .APP and
    .FXP files, are compatible with FoxPro version 2.6 for UNIX. To run
    applications or programs from platforms other than MS-DOS, you should
    rebuild or recompile them.
    ------------------------------------------------------------------------

    Question 4

    Can I distribute my FoxPro version 2.6 for UNIX applications?

    Answer 4

    To distribute your application or executable file, you must purchase
    the Microsoft FoxPro Runtime and install it in your FoxPro directory.
    Each copy of the application distributed must have its own copy of
    the Runtime.
    ------------------------------------------------------------------------

    Topic 4: Printing Issues
    ========================

    Overview of Questions
    ---------------------
    1  When I try to print boxes, ASCII characters are printed instead of
       boxes. How can I correct this problem?
    2  I'm using the Relational Query By Example (RQBE) window to send data
       to a report. The data in the report is incorrect; the report prints
       the same record over and over. How can I correct this problem?
    3  Why can't I select the Printer Driver check box in the Printer
       Setup Dialog box?
    4  I can't make the printer drivers work in an executable file. How can
       I correct this problem?
    5  How do I start a print job from a page other than page 1?
    6  I get the following error "Cannot write to read-only file" when
       printing a report. How can I correct this problem?
    7  I get an extra blank line when printing labels. How can I correct
       this problem?
    8  I have NewPage and ResetPage enabled in my data grouping but my page
       numbering is not reset to 1. How can I correct this problem?
    ------------------------------------------------------------------------

    Question 1

    When I try to print boxes, ASCII characters are printed instead of
    boxes. How can I correct this problem?

    Answer 1

    If you are using an HP LaserJet printer, the default character set does
    not include line drawing characters. You can change the default
    character set by using the controls on the front panel of the printer.
    You will want to set your default to the PC-8 character set.

    If you are not using an HP LaserJet printer and are using printer
    drivers, in the Printer Setup dialog, specify a printer setup
    appropriate for your printer. If you are already using a printer
    driver, modify the P_CODES database in order to send the proper code
    for your printer, and rebuild the genpd.app file. If you aren't using a
    printer driver, send the proper escape codes to the printer before you
    print using the ??? command.
    ------------------------------------------------------------------------

    Question 2

    I'm using the Relational Query By Example (RQBE) window to send data to
    a report. The data in the report is incorrect; the report prints the
    same record over and over. How can I correct this problem?

    Answer 2

    When you created the report, you used alias names in your field
    definitions. To correct the report, simply remove the alias names. For
    example, a field containing CUSTOMER.NAME should be modified to contain
    only NAME.
    ------------------------------------------------------------------------

    Question 3

    Why can't I select the printer driver check box in the Printer Setup
    dialog box?

    Answer 3

    This problem occurs if you are missing the genpd.app file, if the
    _GENPD memory variable is set incorrectly, if the resource file is
    turned off, or if the foxuser file is missing, damaged, or marked as
    read-only.
    ------------------------------------------------------------------------

    Question 4

    I can't make the printer drivers work in an executable file. How can I
    correct this problem?

    Answer 4

    Open the project to make sure that the genpd.app file is included in
    the project as an application. If it isn't included, add genpd.app to
    the project as an application.

    To add genpd.app as an application, choose the Add push button. In the
    dialog that appears, choose Application from the Type popup, select
    genpd.app and then choose the Add push button.

    NOTE: genpd.app is automatically marked as an excluded project
    element.

    Rebuild the project and your executable file. Make sure that you
    distribute the genpd.app, foxuser.dbf, and foxuser.fpt with your
    executable file.
    ------------------------------------------------------------------------

    Question 5

    How do I start a print job from a page other than page 1?

    Answer 5

    To start a print job at a location other than page 1, set _PBPAGE to the
    number of the page at which printing should start and create a program
    that uses the PRINTJOB...ENDPRINTJOB commands.

    Using the _PBPAGE variable to specify the page number where a print job
    starts does not work outside of PRINTJOB...ENDPRINTJOB.

    For example, suppose your printer jammed on page 75 of a 100-page report
    and all output from page 75 through 100 was lost. The code to re-create
    the last 25 pages is as follows:

           _PBPAGE=75
           PRINTJOB
           REPORT FORM test.FRX ENVIRONMENT PDSETUP TO PRINT
           ENDPRINTJOB

    Or, if you just wanted to only print page 75, then set "_PBPAGE=75" and
    "_PEPAGE=75" in the previous example.
    ------------------------------------------------------------------------

    Question 6

    I get the following error "Cannot write to read-only file" when printing
    a report. How can I correct this problem?

    Answer 6

    Given the following circumstances, the error message "Cannot write to a
    read-only file" will occur when you try to print a report from within
    an application (.app) or an executable (.exe) program:

       - The resource file is included in the project.

       - The resource is set to the included filename.

       - The REPORT FORM <name> PDSETUP TO PRINT or LABEL FORM <name>
         PDSETUP TO PRINT command is issued.

    There are two ways to avoid this problem:

       - Remove PDSETUP from the command.

         -Or-

       - Mark the resource file as excluded and ship it along with the .app
         or .exe file.
    ------------------------------------------------------------------------

    Question 7

    I get an extra blank line when printing labels. How can I correct
    this problem?

    Answer 7

    This behavior existed in dBASE III and FoxBASE. It was changed in
    FoxPro version 1.02. However, to maintain compatibility with the large
    installed base of Xbase applications, a design decision was made to
    revert to the original behavior.

    To work around this problem, print the label form to a file, open the
    file with low-level file functions, remove the carriage return/linefeed
    (CR/LF) characters and send the file to the printer using the UNIX cp
    command. For example:

       *--Set the number of lines printed per page and print to a file.
       _PLENGTH=56
       LABEL FORM <form name> ENVIRONMENT PDSETUP TO FILE temp.txt

       *--Open file and replace the CR/LF pair with null characters.
       filehand=FOPEN('temp.txt',2)
       =FGETS(filehand)
       =FSEEK(filehand,-2,1)
       =FWRITE(filehand,chr(0)+chr(0))
       =FCLOSE(filehand)

       *--Copy the file to printer and prevent the appearance of the screen.
       HIDE WINDOW SAVE ALL
       RUN lp -s -dhplaser temp.txt
       SHOW WINDOW ALL
    ------------------------------------------------------------------------

    Question 8

    I have NewPage and ResetPage enabled in my data grouping but my page
    numbering is not reset to 1. How can I correct this problem?

    Answer 8

    The report has a Bottom Margin setting greater than 0 (zero).

    Set Bottom Margin to 0 and add the necessary lines to the Page Footer
    band. For example, if Bottom Margin is set to 2, reset it to 0 and add
    two lines to the Page Footer band.
    ------------------------------------------------------------------------

    Topic 5: Screens
    ================

    Overview of Questions
    ---------------------
    1  Every time I try to generate a specific screen, I have to add my
       supporting screens to the screen set. How can I avoid this problem?
    2  When I create a screen set with more than one window, how do I move
       the cursor from one window to the next?
    3  How do I coordinate Browse windows with screens?
    4  How do I page through a format file that contains a READ?
    5  The Cycle option does not work for desktop screens. How can I
       correct this?
    6  When I create a screen in FoxPro version 2.6 for UNIX, or transport a
       screen from FoxPro version 2.6 for UNIX, I don't see any UNIX objects.
       Why?
    ------------------------------------------------------------------------

    Question 1

    Every time I try to generate a specific screen, I have to add my
    supporting screens to the screen set. How can I avoid this problem?

    Answer 1

    To save these options, you must create a project and include the
    screens as a screen set.
    ------------------------------------------------------------------------

    Question 2

    When I create a screen set with more than one window, how do I move the
    cursor from one window to the next?

    Answer 2

    If all the windows in your screen set are controlled with one READ
    command, use the Page Up key, the Page Down key, or modify the value of
    the _CUROBJ system memory variable to cycle through the windows of your
    screen set. If any one of the windows in your screen set is not
    controlled by the READ command, such as a Browse window, then you must
    press CTRL+F1 to cycle through the screen set.
    ------------------------------------------------------------------------

    Question 3

    How do I coordinate Browse windows with screens?

    Answer 3

    Page D2-96 of the FoxPro Developers Guide give samples for coordinating
    Browse windows with screens but omits the SAVE clause in the example.
    If the optional BROWSE parameter SAVE is omitted, the Browse window
    will close as soon as any other object is clicked.

    The code example should be changed to read as follows:

           IF NOT WVISIBLE("Client List")
              BROWSE NORMAL NOWAIT NODELETE LAST TITLE "Client List" ;
                 NOAPPEND NOMENU SAVE FIELDS company ;
                 WHEN showgets()
           ENDIF

           IF NOT WVISIBLE("Account Details")
              SELECT details
                 BROWSE NORMAL NOWAIT NODELETE LAST TITLE "Client List" ;
                    NOAPPEND NOMENU SAVE  ;
                    FIELDS ;
                    Trans_type:10, ;
                    Trans_date:10, ;
                    Amt:7,Service
              SELECT clients
           ENDIF
    ------------------------------------------------------------------------

    Question 4

    How do I page through a format file that contains a READ?

    Answer 4

    Pressing the PAGE UP and PAGE DOWN keys skips one record at a time,
    forward or backward, in the database and also refreshes the GETs on
    the screen.

    Objects can be placed on different pages or different screens by
    placing a READ command in the format file. The READ command should be
    placed after the last GET that would appear on each screen. The
    following format file example places two objects on the first screen
    and two more on the second screen. To display the objects that are on
    the next screen, press the Page Up or Page Down key.

           @5,1 GET <var1>
           @6,1 GET <var2>
           READ
           @5,1 GET <var3>
           @6,1 GET <var4>
    ------------------------------------------------------------------------

    Question 5

    The Cycle option does not work for desktop screens. How can I
    correct this?

    Answer 5

    The Cycle option on the Window menu is designed to switch between
    windows defined on the desktop. When a screen set contains several
    windows and a desktop screen, Cycle stops on the desktop screen. This
    is normal behavior, since the Cycle command is intended to be used with
    window screens, not the desktop.

    To work around this behavior, define a window with no borders instead
    of using a desktop screen. This will produce a window that looks like
    the desktop.

    The Cycle option is used for cycling through window screens in a screen
    set or windows defined on the desktop. The shortcut key CTRL+F1 can
    also be used to cycle through windows on the desktop.
    ------------------------------------------------------------------------

    Question 6

    When I create a screen in FoxPro version 2.6 for UNIX, or transport a
    screen from FoxPro version 2.6 for UNIX, I don't see any UNIX objects. Why?

    Answer 6

    FoxPro version 2.6 for UNIX objects are very similar to FoxPro version 2.6
    for MS-DOS objects. Therefore, an additional object type is not necessary
    and your UNIX objects will show up as MS-DOS objects.
    ------------------------------------------------------------------------

    Topic 6: Importing Data
    =======================

    Question 1

    How do I import a data file into Microsoft FoxPro for UNIX?

    Answer 1

    To import a data file, use either the IMPORT command or the APPEND FROM
    command. If you're receiving the error message "String too long to fit,"
    make sure that no "field" in the source data file exceeds the field
    capacity for a FoxPro table. See the System Capacities topic in Help
    for additional information. A wide range of file formats is supported.
    See the IMPORT command topic in the Language Reference manual for a
    complete list of the supported file formats.
    ------------------------------------------------------------------------

    Topic 7: BROWSE Command
    ======================

    Overview of Questions
    ---------------------
    1  I modified the structure of my database, but when I use the BROWSE
       command to view the file, I don't see the changes. How can I correct
       this problem?
    2  When I press the CTRL+N key combination in my program to append a
       new record in the Browse window, I get the musical note instead. How
       can I correct this problem?
    ------------------------------------------------------------------------

    Question 1

    I modified the structure of my database, but when I use the BROWSE
    command to view the file, I don't see the changes. How can I correct
    this problem?

    Answer 1

    You are most likely using the BROWSE command from the System menu or
    the View panel, or you are issuing a BROWSE LAST or BROWSE PREFERENCE
    command from the Command window. To see these structural changes, you
    must first issue a plain BROWSE command from the Command window to
    display the new default representation of the database.
    ------------------------------------------------------------------------

    Question 2

    When I press the CTRL+N key combination in my program to append a new
    record in the Browse window, I get the musical note instead. How can I
    correct this problem?

    Answer 2

    CTRL+N is a shortcut key combination associated with the System menu.
    In your program, you must issue the SET SYSMENU ON command and/or use a
    BROWSE command instead of the BROWSE NOMENU command.
    ------------------------------------------------------------------------

    Topic 8: Creating Applications and Executables
    ==============================================

    Overview of Questions
    ---------------------
    1  I've created an application that doesn't allow me to edit my
       database files. How can I correct this problem?
    2  My executable file runs correctly under the development version, but
       I receive the error message "Feature not available" under the
       stand-alone version. How can I correct this problem?
    ------------------------------------------------------------------------

    Question 1

    I've created an application that does not allow me to edit my database
    files. How can I correct this problem?

    Answer 1

    Including the database in the project automatically makes these files
    read only. Mark your database as excluded in the project, then rebuild
    your application. You must distribute these files to your end users.
    ------------------------------------------------------------------------

    Question 2

    My executable file runs correctly under the development version, but I
    receive the error message "Feature not available" under the stand-alone
    version. How can I correct this problem?

    Answer 2

    First, check the "Features Not Available" list in the FoxPro for UNIX
    Runtime User's Guide. Certain features used for development aren't
    available in the applications and executables you create. If you still
    encounter problems, it's possible that you're using macro substitution
    in your program. The recommended work around is to set up a statement
    which causes the compiler to see the possible options for the
    macro-substituted commands so that they will be compiled into the .exe
    file. For example:

           IF .F.
                  MODIFY REPORT dummy
                  MODIFY LABEL dummy
           ENDIF

    This code allows the compiler to see the MODIFY REPORT and MODIFY LABEL
    commands, but because it is never executed, the report and label names
    can be meaningless (dummy).
    ----------------------------------------------------------

                       =============
                       end of readme
                       =============

Additional query words: FoxUnix

    Keywords          :
    Version           :
    Platform          :
    Issue type        :

Last Reviewed: August 25, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of Use.