                      Welcome to the Quattro Pro
                   Network Installation README File
                  ==================================

 The information presented in this file provides specific
 step-by-step instructions for installing Quattro Pro on a
 non-Novell network.  If you are installing Quattro Pro for use
 on a Novell network, follow the instructions in the Quattro Pro
 User's Guide.  These guidelines apply when Microsoft Windows is
 run locally on each user's workstation as well as when Windows
 is run from a shared directory on the network.  This file
 details installing Quattro Pro on the server, setting up
 additional users, and assigning user's rights.

 The following is an example of a directory structure with a root
 drive letter P.  This structure will be referenced throughout
 this file.  It is merely used as an example; your network
 layout may vary.  

     P:\
     |
     |-- QPW
     |   |
     |   |- SAMPLES
     |   |- TEMPLATE
     |   |- NETFILES
     |   |- QPWPRIV     
     |   |- DBDPRIV
     |
     |-- IDAPI
     |
     |-- OBEX
     |   |
     |   |- BIN
     |   |- BOOK\BOOK
     |
     |--POST
     |    |
          |- USER1
          |- USER2

     C:\OBJSTORE (Can be on a private drive.)

 The OBJSTORE directories and POST directories can be created
 after installation.  Quattro Pro will create the remaining
 directories needed during installation.  Also, after
 installation, the QPWPRIV and DBDPRIV directories can be removed
 and re-created for each user in an area where they have
 exclusive rights.


       INSTALLING QUATTRO PRO ON THE NETWORK SERVER

 1. Choose File | Run from the Windows Program Manager, type
    A:INSTALL.EXE (or B:INSTALL.EXE if installing from the B:
    drive) and choose OK.  Select Default, Minimum, or Custom and
    choose Next.

 2. Specify your name and the company name (this information is
    required) and choose Next.

 3. Specify a directory on the network for the Quattro Pro files
    and choose Next.

 4. If you select the Custom installation option, choose which
    parts of the product you would like to install.

 5. If you are installing Quattro Pro for multiple users, choose
    Next.  Otherwise, select "No, I want to install a single-user
    setup" and then choose Next.

 6. Specify a directory for the Object Exchange files and choose
    Next.  Object Exchange (OBEX) allows you to share information
    between different applications and different users of the
    same application.  In Quattro Pro, you can share notebooks,   
    notebook pages, or sets of notebook pages.

 7. If you selected the Custom installation option, specify the
    full path for the following directories:

    QPW Samples      Sample files included with Quattro Pro.

    QPW Templates    Template files included with Quattro Pro.

    Object Exchange  Executables
                     By default, this points to the OBEX\BIN
                     directory.  It is recommended that this not
                     be changed.

    Object Store     Each user should have their own Object Store
                     directory so you may specify the Object
                     Store directory for this installation
                     machine.

     Shared Code     If you already have a shared code directory,
                     specify this directory.

 8. Specify a directory for the IDAPI program files and one for
    the configuration files.  IDAPI is the tool Quattro Pro,
    Database Desktop, and Paradox for Windows use to access
    external database tables.  The default IDAPI directory will
    be a directory named IDAPI.  It is recommended that the IDAPI
    program files be placed in a separate directory (e.g.,
    P:\IDAPI) so that all applications that use IDAPI will have
    access to them.  It is also recommended that the IDAPI
    configuration file be placed in a separate directory.  If a
    previous version of Quattro Pro or Paradox for Windows has
    been installed on the network, which used the ODAPI
    technology, the install process may automatically detect the
    path to the ODAPI directory and default to that directory.    
    It is recommended that the IDAPI files be installed into a
    directory different from the ODAPI files.  Choose Next when
    you have typed the full path to the IDAPI directories.

 9. Choose Install.  The installation process will begin.  Insert
    Quattro Pro disks as requested by the install program.

10. After Quattro Pro has been installed, the README file can be
    displayed.  The README file is placed in the \QPW directory. 
    It is strongly recommended that you read this file and make
    it available to all users of Quattro Pro.  It contains
    important information not found in the manuals.

    Quattro Pro is now installed, configured, and ready to run
    only on your system.  Setting up additional users will be
    discussed in a later section.


             RUNNING THE IDAPI CONFIGURATION UTILITY

 Quattro Pro and Database Desktop can read and write dBASE,
 Paradox, and SQL tables.  In order to interact with these file
 formats, IDAPICFG.EXE must be run.

 1. Run the IDAPI configuration utility and choose Driver Name:
    Paradox.

 2. If any version of Paradox is installed on the network, there
    is already a directory for network control files (i.e.,
    PDOXUSRS.NET for Paradox for DOS 4.0 or Paradox for Windows 
    4.5 users and PARADOX.NET for Paradox for DOS 3.5 users). 
    Enter the complete path for this directory in the Network
    Control File Directory field.  If you have not yet set up a
    directory for network control files for other applications,
    specify any directory to which all users have rights to
    search, read, delete, and modify files (e.g.,
    P:\QPW\NETFILES).

    From the menu, choose Pages | System.  Local share tells
    IDAPI how to treat the computer's hard drive (referred to as
    the local drive).  If Local Share is "TRUE", IDAPI will
    treat the local drive like a network drive.  This will allow
    you to safely share locally stored tables with non-IDAPI
    applications that access the tables.  When Local Share is
    "FALSE", IDAPI turns off the data locks on local files.  If
    you are sharing data with non-IDAPI applications, this
    leaves you unprotected from data corruption.  Having Local
    Share disabled may provide a slight performance increase in
    accessing local data.

 3. Choose File | Save.  Choose File | Exit.

 For more information on the IDAPI configuration utility, refer
 to the utility's online help.


                SETTING UP ADDITIONAL USERS

 Each user's system will now need to be modified in order for the
 user to access Quattro Pro, Database Desktop, Data Modeling
 Desktop, and Object Exchange or OBEX.  A detailed description of
 how to do this is listed below.  The WIN.INI file needs a
 section to define IDAPI, Database Desktop, and Object Exchange. 
 Each user also will need a Quattro Pro Program Group and icons
 for Quattro Pro, Database Desktop, Data Modeling Desktop, Object
 Exchange, IDAPI Configuration Utility, and the README file. 
 Certain files must be copied into each users Windows directory
 (e.g., C:\WINDOWS) and, if Windows is run locally, Windows
 System directory (e.g., C:\WINDOWS\SYSTEM).  Users can register
 Quattro Pro as an OLE client if desired.

 1. All changes that were added to your WIN.INI file during
    installation need to be copied to each user's WIN.INI file. 
    The following is a list of sections that should be added:

     [IDAPI]
     CONFIGFILE01=path
     DLLPATH=path

     [DDE Servers]
     DBD=path
     OBEX=path
     DMODELER=path

     [DBD]
     WORKDIR=path
     PRIVDIR=path

     [OBEX]
     OBEXDIR=path
     WORKDIR=path

 Description of the [IDAPI] section:
 -----------------------------------

     CONFIGFILE01= the full path (including drive and directory)
                   should point to the IDAPI configuration file
                   (e.g., P:\OFFICE\SHARED\IDAPI\IDAPI.CFG).

     DLLPATH=      the full path (including drive and directory)
                   should point to the IDAPI files (e.g.,
                   P:\OFFICE\SHARED\IDAPI).

 Description of the [DDE Servers] section:
 -----------------------------------------

     DBD=          the full path (including drive and directory)
                   to Database Desktop (e.g., P:\QPW\DBD).
 
     OBEX=         the full path (including directory) to the
                   OBEX executable file (e.g., P:\OBEX\BIN\OBEX).
  
     DMODELER=     the full path (including directory) to Data
                   Modeling Desktop (e.g., P:\QPW\DMODELER).

 Description of the [DBD] section:
 ---------------------------------

     WORKDIR=      the directory that each user will use as a
                   default working directory for Database
                   Desktop.  Normally, this is where most of the
                   common files are located (this is easily
                   changed from within Database Desktop to
                   accommodate individual users).  This directory
                   cannot be the same as any other user's private
                   directory.

     PRIVDIR=      this should point to a directory that is
                   exclusive to the user (e.g., F:\USER or
                   C:\TEMP).  Database Desktop uses the private
                   directory to store temporary files that are
                   needed during normal operation (e.g.,
                   ANSWER.DB).  Under no circumstances can more
                   than 1 user access the same private directory.

                   The private and working directories can either
                   be modified here or from Database Desktop. 
                   The WORKDIR and PRIVDIR directories can also
                   be located on each user's local hard drive. 

Description of the [OBEX] section:
----------------------------------

     OBEXDIR=      this should point to the OBEX\BIN directory
                   (e.g., P:\OBEX\BIN).  Each user must have a
                   separate OBJSTORE directory (e.g., 
                   C:\OBJSTORE).  If the OBJSTORE directory is on
                   a local hard drive, the user has access to
                   received objects even when the network is not
                   connected.

     WORKDIR=      this should be the same as the OBEX\BIN
                   directory (aka OBEXDIR) unless a previous
                   installation of OBEX placed it somewhere else
                   (e.g., C:\WINDOWS).

 In many cases, the process of modifying the WIN.INI file can
 be made less time consuming by creating a text file (e.g.,
 QPW.TXT) that has all the settings described above.  This text
 file can be appended to each user's WIN.INI file with the DOS
 TYPE command:

          TYPE QPW.TXT>>WIN.INI

 Execute this command from the directory where the WIN.INI
 and QPW.TXT files are located or specify the appropriate path
 along with each file name.  In order for this to work, all the
 directories specified in the WIN.INI must be the same for each
 user.  This can be accomplished by using local hard drive
 directories as the private directory for Database Desktop and 
 the OBJSTORE directory or by mapping these individual
 directories to the same drive letter for each user.

 For example, if each user has a private directory on a
 network drive under the USERS subdirectory on a Novell network,
 the command:

          MAP ROOT U:=\USERS\%Login_Name

 will create a map to each user's private directory under the
 \USERS directory.  This allows everyone to have their PRIVDIR
 setting point to U:\.

 NOTE:  This procedure may fail if there is an existing
 [IDAPI], [DDE Servers], [DBD], or [OBEX] section in the WIN.INI. 
 Verify that these sections are not already in the .INI file
 before appending new sections.

 2. Add a Quattro Pro program group and program items (icons) for
    Quattro Pro, Database Desktop, Data Modeling Desktop,
    Object Exchange, IDAPI Configuration Utility, and README.TXT. 
    To create the program group and items, choose File | New from
    the Program Manager.  Choose Program Group and choose OK. 
    Enter the Description and Group File and choose OK.  To
    create icons, make this group the active group and choose
    File | New again.  Choose Program Item and then choose OK. 
    Browse for QPW.EXE located in the Quattro Pro directory
    (e.g., P:\QPW) and choose OK.  Repeat this process for
    Database Desktop (P:\QPW\DBD.EXE), Data Modeling Desktop
    (P:\QPW\DMODELER.EXE), Object Exchange (P:\OBEX\OBEX.EXE),
    and IDAPI Configuration Utility (P:\IDAPI\IDAPICFG.EXE).  For
    README.TXT, the Command line should specify NOTEPAD followed
    by the full path to README.TXT.  For example:

         NOTEPAD P:\QPW\README.TXT

 One way to automate this process is to use Windows' Macro
 Recorder to record the process of creating a program group for
 Quattro Pro and adding the program icons (see your Windows
 manual for more information about the Macro Recorder).  If you
 save the macro file in the Windows directory as QPWGRP.REC and
 name the macro QPW for example, each user can automatically set
 up a group by starting Windows with the command WIN QPWGRP.REC,
 then double clicking on the Quattro Pro icon.

 3. If Windows is run locally (i.e., on each user's workstation),
    copy the following files from your Windows System directory
    to each user's Windows System directory:

          TTYTWIN.DRV
          BWCC.DLL

 and copy the following files from your Windows directory to
 each user's Windows directory:

          WINHELP.EXE 
          WINHELP.HLP 
          QPW.INI
          OBEX.INI

 4. If Windows is run from the network, the above files are
    copied into the shared Windows directories during the
    installation process.  However, you must still copy BWCC.DLL,
    QPW.INI, and OBEX.INI to each users Windows directory.  If
    you wish to set defaults in Quattro Pro for all users, start
    Quattro Pro and set the defaults before you copy the QPW.INI.

 Add a search drive for the IDAPI directory (e.g., P:\IDAPI),
 or include it in each user's path.  On a Novell network, a
 convenient way to do this is to add the search drive definition
 to the network system login script using the MAP command.  For
 example:

          MAP INSERT S1:=SERVER1/VOL:IDAPI

 The above MAP command inserts the IDAPI directory as search
 drive 1.  SERVER1 is the name of the server on which the IDAPI
 files are installed and VOL is the volume name.  

 A personal login script can also be used to add the IDAPI
 directory to the path.

 Decide if the users will be allowed to create aliases in
 Database Desktop and Paradox.  An alias is a name given to a
 directory on the hard disk or the network.  

 If you want to give the users the ability to create aliases,
 each user must have an IDAPI.CFG file located in a directory to
 which they have full rights (i.e., hard disk or private
 directory).  You must run the IDAPI configuration utility on the
 individual workstation to specify the path to the user's hard
 disk or private directory.

 If you do not want to give the users the ability to create
 aliases, you can create default aliases and leave the IDAPI.CFG
 file in the IDAPI configuration directory on the network which
 you specified during installation.  The users will not have the
 necessary rights to make changes in the IDAPI configuration
 utility or to create aliases.  You will still need to run the
 IDAPI configuration utility on each workstation to update the
 [IDAPI] section of the individual WIN.INI files.

 5. If you want to use the LAN transport, set up a LAN post
    office directory.  Refer to the Users Guide and the text file
    LANINFO.TXT in the Quattro Pro directory for more
    information.


                    ASSIGNING NETWORK RIGHTS

 In order for Quattro Pro to run properly, users must have the
 proper rights to the various directories involved with
 Quattro Pro.  The names of rights on various networks differ. 
 The following is a list that describes the minimum each user
 must be able to do in each directory.  See your network
 documentation for information on how to set these rights.  For
 reference, the rights for NetWare 386 are given in parenthesis:


 QPW            Read files, open files, search in the directory.
 (READ, FILESCAN)

 IDAPI           Read files, open files, search in the directory. 
 (READ, FILESCAN)

 OBEX            Read files, open files, search in the directory. 
 (READ, FILESCAN)

 BOOK\BOOK       All rights except the right to control other
                 user's access to the directory.  (READ, WRITE,
                 FILESCAN, ERASE, CREATE, MODIFY) 

 OBJSTORE        All rights except the right to control other
                 user's access to the directory.  (READ, WRITE,
                 FILESCAN, ERASE, CREATE, MODIFY)

 QPW\SAMPLES     Read files, open files, search in the directory.
 (READ, FILESCAN)

 QPW\TEMPLATE    Read files, open files, search in the directory.
 (READ, FILESCAN)

 QPW\NETFILES    All rights except the right to control other
                 user's access to the directory and the rights to
                 delete a file. The user must be able to read,
                 open, and modify files as well as search in the
                 directory. (READ, WRITE, FILESCAN, CREATE,
                 MODIFY)

 OBJSTORE       All rights except the right to control other
                user's access to the directory.  (READ, WRITE,
                FILESCAN, ERASE, CREATE, MODIFY)

 PRIVDIR        All rights except the right to control other
                user's access to the directory.  (READ, WRITE,
                FILESCAN, ERASE, CREATE, MODIFY)

 WORKDIR        All rights except the right to control other
                user's access to the directory.  (READ, WRITE,
                FILESCAN, ERASE, CREATE, MODIFY)

 NOTE: Users can modify their working and private directories
 from within Database Desktop.  Make sure one or both of
 these directories are not changed to a directory where
 sufficient rights are not available.  If this happens,
 Database Desktop will not start once exited.  To regain
 access to Database Desktop, edit the WIN.INI file and change
 the WORKDIR and/or PRIVDIR settings (in the [DBD] section)
 to a directory with sufficient rights.