=================================================================
README.TXT
=================================================================
This file explains updates to Novell InForms 4.1 that address
some issues that arise when the application is running under
Windows NT and Windows 3.1.  If you want to update InForms 4.1, you
must have previously installed the application.  The problems this
patch fixes are listed at the end of this file.

To apply the patch, you must use a utility called PATCH.EXE (from
Pocket Soft, Inc.), along with the accompanying .RTP files. The
patch updates files in the directories specified below.  If you are
running InForms 4.1 from the network, your network administrator
may need to update the files if you do not have the rights to do so.


UPDATED FILES
=============
This utility updates the files listed below.

The file INF1.RTP updates the following files in the
InForms 4.1 directory
(in a standard installation, this would be C:\INF41):
               <SIZE> <DATE>   <TIME>     <SIZE> <DATE>   <TIME>
CLPLIB.DLL     116576 03/31/95 4:10 am TO:        03/31/95 4:10 pm
DBCRT.DLL       38880 03/31/95 4:10 am TO:        03/31/95 4:10 pm
DBLNK.DLL       29776 03/31/95 4:10 am TO:        03/31/95 4:10 pm
DPLIB.DLL       29248 03/31/95 4:10 am TO:        03/31/95 4:10 pm
FDWIN41.EXE    888384 03/31/95 4:10 am TO:        03/31/95 4:10 pm
FFWIN41.EXE    604048 03/31/95 4:10 am TO:        03/31/95 4:10 pm
FLMLIB.DLL     327886 03/31/95 4:10 am TO:        03/31/95 4:10 pm
FPLIB.DLL      116784 03/31/95 4:10 am TO:        03/31/95 4:10 pm
FSWIN41.EXE    109344 03/31/95 4:10 am TO:        03/31/95 4:10 pm
ININST.EXE     421952 03/31/95 4:10 am TO:        03/31/95 4:10 pm
INSTALL.DAT      9856 03/31/95 4:10 am TO:        03/31/95 4:10 pm
INMEMDLL.DLL    17147 03/31/95 4:10 am TO:        03/31/95 4:10 pm
INQBE.DLL      180288 03/31/95 4:10 am TO:        03/31/95 4:10 pm
INQBEUS.DLL     40384 03/31/95 4:10 am TO:        03/31/95 4:10 pm
INSEC.DLL       50432 03/31/95 4:10 am TO:        03/31/95 4:10 pm
INTT41.DLL      74080 03/31/95 4:10 am TO:        03/31/95 4:10 pm
NOTELIB.DLL     37680 03/31/95 4:10 am TO:        03/31/95 4:10 pm
QBELIB.DLL      85328 03/31/95 4:10 am TO:        03/31/95 4:10 pm
README.IN       24289 03/31/95 4:10 am TO:        03/31/95 4:10 pm
SMLIB.DLL       38320 03/31/95 4:10 am TO:        03/31/95 4:10 pm


The file INFPF2.RTP updates the following files in the
PerfectFit directory
(in a standard installation, this would be C:\OFFICE\SHARED\WPC20):
               <SIZE> <DATE>   <TIME>     <SIZE> <DATE>   <TIME>
DTWIN20.EXE     86912 12/09/94 3:00 am TO:        12/09/94 3:01 pm
SHWIN20.DLL   1176832 12/09/94 3:00 am TO:        12/09/94 3:01 pm
SHWINB20.DLL   586208 12/09/94 3:00 am TO:        12/09/94 3:01 pm
SHWINX20.DLL   109664 11/04/94 6:10 am TO:        12/09/94 3:01 pm
SHX20US.DLL     21216 11/04/94 6:10 am TO:        12/09/94 3:01 pm
SPWIN20.DLL     69600 11/04/94 6:10 am TO:        12/09/94 3:01 pm
VWRIN.DLL      185024 03/31/95 4:10 am TO:        03/31/95 4:10 pm


INSTALLING THE UPDATES
======================
To install the updates, you must first find out where your InForms
4.1 and PerfectFit directories are. To do so,
 
1    Start InForms 4.1.
2    Select About InForms from the Help menu.
3    Make a note of the path beside Program Release; this is your
     InForms 4.1 directory.
4    Make a note of the path beside Shared DLL Release; this is
     your PerfectFit directory.
5    Exit InForms.
6    Close all other Novell applications. You cannot apply the
     PerfectFit patch while any other Novell applications are
     running.

After you have identified the location of your InForms 4.1 and
PerfectFit directories,

1    Go to a DOS prompt.
2    Change to the drive and directory where the update disk
     exists (usually A:).
3    At the DOS prompt, type:
       PATCH INF1.RTP C:\INF41 (replace C:\INF41 with the path
         to your InForms 4.1 directory if that directory is in   
         another location), and wait for the patch to update the
         files.
4    At the DOS prompt, type:
       PATCH INFPF2.RTP C:\OFFICE\SHARED\WPC20 (replace
         C:\OFFICE\SHARED\WPC20 with the path to your PerfectFit
         directory if that directory is in another location),
         and wait for the patch to update the files.


TROUBLESHOOTING
===============

If any errors or warnings occur while you are applying the patches,
a PATCH.ERR file is created in the target directory where the patch
is applied.

If PATCH.EXE cannot locate the files that need to be patched, the
following message is displayed:

     Warning wpt0015: Old File does not exist

This message may indicate one or more of the following situations:

     *    You have previously deleted one or more files from the
          original InForms 4.1 installation.

     *    You are trying to patch the wrong version of InForms. You
          may need to reinstall the original InForms 4.1 files
          before you apply the patch.

If PATCH.EXE determines that a file does not need to be patched,
the following message is displayed:

     New Version of File FILENAME already exists.

This message may indicate that you have already applied the patch.
PATCH.EXE has verified that your software is up-to-date; you do not
need to take any further action.


ADDITIONAL FILES
================
A) NWCALLS.DLL
B) CTL3DV2.DLL

A) The NWCALLS.DLL file was not being installed properly in a
network server installation and in a workstation installation with
InForms running from the network.

If you have a standard installation running InForms from a local
drive, NWCALLS.DLL is already properly installed; you do not need
to do anything with this file. If you have a network server
installation, you need to copy the file to the "OLE2" subdirectory
from the PerfectFit directory. If you already have a NWCALLS.DLL
file in the "OLE2" subdirectory and it has a later date and time
than the one supplied with the patch, you do not need to continue
with the following steps.

After you have identified the location of your PerfectFit directory
for a server installation,

1    At the DOS prompt, type:
       COPY NWCALLS.DLL W:\WIN\OFFICE\SHARED\WPC20\OLE2
         (replace W:\WIN\OFFICE\SHARED\WPC20 with the path to your
         Shared Code directory).

After you have applied the above patch and copied the file to the
"OLE2" PerfectFit subdirectory of a network server installation,
all new workstation installations will correctly put this file into
the local "\WINDOWS\SYSTEM" directory. For existing workstation
installations, you need to manually copy the file to the local
"\WINDOWS\SYSTEM" directory or run the install program again.


B) The CTL3DV2.DLL file was not being installed properly in all
types of installations. If you have a standard installation running
InForms from a local drive, you need to copy CTL3DV2.DLL to the
local "\WINDOWS\SYSTEMS" directory if it is not already there. To
do so,

1    At the DOS prompt, type:
       COPY CTL3DV2.DLL C:\WINDOWS\SYSTEM (replace
         C:\WINDOWS\SYSTEM with the path to your installed windows
         system directory).

If you have a network server installation, you need to copy this
file to the "OLE2" subdirectory off the PerfectFit directory. If
you already have this file in the "OLE2" subdirectory and the file
has a later date and time than the one supplied with the patch, you
do not need to continue with the following steps.  After you have
identified the location of your PerfectFit directory for a server
installation,

1    At the DOS prompt, type:
       COPY CTL3DV2.DLL W:\WIN\OFFICE\SHARED\WPC20\OLE2
         (replace W:\WIN\OFFICE\SHARED\WPC20 with the path to your
         Shared Code directory.)

After you have applied the above patch and copied the file to the
"OLE2" PerfectFit subdirectory of a network server installation,
all new workstation installations will correctly put this file into
the local "\WINDOWS\SYSTEM" directory. For existing workstation
installations, you need to manually copy the file to the local
"\WINDOWS\SYSTEM" directory or run the install program again.


PROBLEMS FIXED WITH THIS PATCH
==============================

  Data Links
     *  Under some conditions, read-only database fields were
        written to the database when a write object link was
        updated.
     *  A sorting problem sometimes caused a "Corrupt File,
        Datalinks Lost" error message to be displayed when there
        were hundreds of fields on a valid form.

  Data Tables
     *  Text was not always justified correctly when records
        scrolled into view and when they were edited.
     *  Under certain conditions, a GPF occurred when data table
        rows were being printed on attachment pages.
     *  When a memo field was defined within a data table and it
        had enough text to wrap, only the first line of text was
        printed on any attachment pages.
     *  When the primary field was on one page and the data table
        was on another page, "A primary record must be locked
        before entering the data table" message was displayed
        incorrectly.

  Delrina Form Import
     *  The import incorrectly excluded earlier versions of
        Delrina Forms from being imported (Pre-PerForm Pro Plus).

  Formulas
     *  Under certain conditions, @DELETEREC() generated an
        "Internal Memory Error" message.
     *  A GPF occurred in Filler if a formula went to two different
        linked forms.
     *  The @RESETOBJ() formula did not work for table cells.
     *  Under certain conditions, an object's value was cleared
        incorrectly when it called an Independent formula.
     *  "Open" type formulas were not firing on @NEWREC() when
        they were attached to Action Button objects.
     *  The @TEXT() function deleted leading zeros of a decimal
        value (e.g., .03 was changed to .3).
     *  A GPF occurred when opening a form in Filler if a change
        formula referenced a multi-record table column using a
        column name reference instead of a column letter
        reference.

  Installation
     *  The file CTL3DV2.DLL was not being installed. (This file
        is needed for the IDAPI configuration utility.)
     *  On a server or workstation installation, the file
        NWCALLS.DLL was not being installed.
     *  Under certain conditions, a GPF occurred after a server
        installation.

  Lotus Notes
     *  Some Lotus Notes forms were not showing in the list of
        tables when a form was being linked to a Lotus Notes
        database.
     *  Querying a Lotus Notes form did not show records that were
        entered using Notes.
     *  A form could not be linked to Lotus Notes Views.

  Object Appearance
     *  If you turned a table cell line off through the Example
        window, you could not turn it back on.
     *  In certain conditions, copying and pasting an object changed
        the copied object font to something different from the
        original font.

  Query
     *  Query catalogs were incorrectly being read in when
        Data-Only (.DO) forms were opened. Query catalogs are
        not valid in .DO forms.
     *  A record could not be deleted from FoxPro and Clipper
        databases if the data had an embedded apostrophe.
     *  The query parse failed when a query was being performed on
        a Clipper database with 1,000 fields.

  README.IN File
     *  Step 3 in the "ACCESS THE Q+E DRIVERS" section incorrectly
        stated that you should rename the INDBLQE.DLL file to
        INDBLIB.DLL. The name of the file you need to rename is
        actually INDBLIB.OLD.

  Text Tool
     *  Hard returns were not counted in Memo fields, which allowed 
        more characters than expected to be entered.
     *  In some cases, character spacing with bold and italic fonts
        was different than the spacing for the regular font in
        InForms 1.0b. 
     *  A memo field with underline set displayed text incorrectly
        in relation to the underlines displayed when a printer was
        selected.

  Windows NT
     *  Global spell-checking produced a GPF under Windows NT.
     *  Tabbing to any field that already contained data produced
        a GPF under Windows NT when Fast Editor was off.