     MAINTREL.TXT -- (c) 1993, Craig L. Jones -- May 16, 1993 -- Page 1


               Notes on the Paradox 4.01 Maintenance Release


     [Late Breaking News: Paradox 4.02 is available.  It does not have
     the secondary index restriction that 4.01 has (see number 2,
     below).]


     1.  PAW and Paradox 4.01

     A maintenance release for Paradox/DOS was released in February.
     The release is designated 4.01 and the files carry the date stamp
     of 1/11/93.  This release fixes a number of minor problems and
     one fairly serious one--a memory leak that occurred whenever a
     pulldown menu was invoked.  This release is especially pertinent
     for users of the Application Workshop, since it relies heavily on
     pulldown menus, both at design-time and at run-time.

     To get a copy of this maintenance release, simply call the
     Borland order desk at (800) 331-0877 and request it.

     The Application Workshop itself does not appear to have changed
     at all in this release.  That is, a comparison of the byte-counts
     of the procs in the two libraries show no differences.


     2.  Secondary Index Changes

     One thing to be aware of with regard to this release is that
     Borland had to add a new restriction to the use of OrderTable
     (the feature that allows you to view a table in an order other
     than by the primary key).  You now cannot edit (or coedit) a
     multi-table form that has an embedded table with a one-to-many or
     one-to-one relationship while the master table in a secondary
     index order.  Borland did, however, provide a new
     function--TableOrder()--that allows PAL programmers to work
     around this restriction.  See section 7 of the HELPME.TXT file.)

     Now, you might wonder how your program will know if it is running
     under 4.01 or 4.00 so that it can decide whether or not a call to
     the new TableOrder() function is legal.  You can't use the
     Version() function, because it only returns a number to one
     decimal point (i.e. 4.0).  The answer is to use the SysInfo To
     dynarray command, and then check the "BUILD" element of the
     dynarray.  (See the PAL manual under SysInfo.)


     3.  Postrecord

     The Postrecord command now causes a run error in certain
     circumstances (as opposed to just returning Retval = False).
     With appropriate error trapping, this allows for more control by
     being able to determine the cause of the failure.


     4.  Other Changes

     We are vaguely aware of only one other correction that 4.01
     addresses (although there are probably others).  We understand
     that 4.01 fixes some problem having to do with group-band sorting

     MAINTREL.TXT -- (c) 1993, Craig L. Jones -- May 16, 1993 -- Page 2


     in a report.


     5.  New Minor Problem with Look-up Tables

     One minor problem was introduced with the 4.01 release.  If you
     have a look-up table with the all-corresponding values option
     set, and one of the values to be copied is a memo field, then the
     value will only be copied if it is longer than the fixed portion
     of the memo field.  The work-around is to either not use memo
     fields in all-corresponding look-up tables, or to make sure that
     all non-blank values are longer than the fixed-length portion of
     the memo (e.g. use M1 instead of, say, M25).

