ANOMALIES UPLOADED ON 02-17-89


                                   ANOMALY6.TXT


In keeping with our commitment to provide you, the user, with support that
will maximize your productivity with the dBASE IV product, we are
continuing our tradition of publishing timely, detailed anomaly and
work-around reports.

The following listing addresses two known anomalies when using dBASE IV. 
Use of these techniques will aid you in avoiding anomalies that have been
reported to our Software Support Center.  This report will be supplemented
as new information is
received.  


*************************************************************************************


                                   ANOMALIES


DBSETUP incorrectly indicates the non-existance of a Math Co-processor

     The DBSETUP:Tools:Review system configuration screen in the
     DBSETUP program incorrectly displays a blank entry (instead of a
     YES) in the Math co-processor field when a math co-processor IS
     installed.  
     
     Indeed, the dBASE IV product DOES recognize and make use of a
     math co-processor to increase performance, even though this
     display error would seem to indicate otherwise.  
     
     Additionally, the same display error occurs in the DMA controller
     field of the DBSETUP:Tools:Review system configuration screen
     when using a DMA controller.
     
===========================================================================


DBSETUP does not save colors in CONFIG.DB

     Defining colors via DBSETUP will reflect the new foreground and
     background color selections on screen, but fails to store the new
     settings to CONFIG.DB.
     
     WORKAROUND:
     
     There are 2 possible workarounds for the above problem:
     
     1)   MODIFY COMMAND CONFIG.DB at the dot prompt and define color with
     a COLOR OF ... = <settings> statement.  Appropriate color <settings>
     are discussed in the "Commands" section, page 3-18 of Language
     Reference.
     
     2)   Delete all of the COLOR OF ... commands from the CONFIG.DB file. 
     It is now possible to run DBSETUP and have the new settings saved to
     the CONFIG.DB file.
     
===========================================================================