Readme file for patches to CA-Clipper 5.2d, ExoSpace 1.0F and DBFCDX.LIB
========================================================================


Notes on additional patch files for CA-Clipper 5.2d
---------------------------------------------------
The OBJ files contained in this archive are to be linked into the application
as FILES. This will overwrite any modules of the same name in the LIBRARIES.

 **** DO NOT EXTRACT AND REPLACE THESE OBJECT FILES FROM THE LIBs ****

This will alter the LIB's byte size, date/time stamp and cause problems with
any future updates to the corresponding LIBs.

             GETS2.OBJ 12982 05-18-94 12:03p

             VMAPI.OBJ  2332 07-12-94 10:41a

              TERM.OBJ 10656 07-18-94  3:23p


 - GETS2.OBJ fixes GPF in PICTURE "@K" clause (introduced in 5.2d)

 - VMAPI.OBJ fixes GPF in repeated SET ORDER TO command (introduced in 5.2d)

 - TERM.OBJ  fixes GPF in ERRORSYS when trying to print a string and there
             is no printer connected and errorblock returns TRUE ( RETRY
             option ).

============================================================================


Notes on additional patch file for CA-Clipper/ExoSpace 1.0f
-----------------------------------------------------------

   EXOSPACE.EXE  643353  06-02-94  1:07p

   A new EXOSPACE.EXE (Version 1.0f-1) is provided to fix the
   Internal Error 332. The Virtual Memory Manager has been
   changed so that it keeps track of the available memory
   accurately and activates the Garbage Collector only when
   it needs to.


============================================================================


Release Notes DBFCDX 3.00
-------------------------

   U.S. version is located in the DBFCDX\US directory.
   DBFCDX.LIB  98227  07-01-94  5:13p

   International version is located in the DBFCDX\INTL directory.
   DBFCDX.LIB  98749  07-01-94  5:14p


1. The locking for DBFCDX 3.00 has been changed from DBFCDX 2.00.  The
   locking scheme now used is compatible with FOXPRO, FOXPRO for Windows,
   SIx 2 and the FOXPRO/ACCESS ODBC Windows driver.  This new locking
   scheme provides for a wider base of compatibility and higher performance.
   There is no need to link CDXLOCK.OBJ anymore.

2. Structural indexes are now always located at the front of the order
   list. This change eliminates confusion as to the location of the
   structural index tags.  Users using the recommended method of
   specifying orders via order names will not notice any difference.

3. Performance has been greatly increased and load size has been lowered.

4. Spurious GPF errors have been fixed.

5. Memo Support has been rewritten to improve reliability.

6. The RTLink Command STACK 0 must be added to base52.lnk for DBFCDX to
   be linked into a PLL file.