Install
     Install provides incorrect information about the total disk space 
     required when selected target drive is other than C.

dBASE
     The maximum value for SET TYPEAHEAD has been reduced to 1600.
     dBASE IV supports 32000. 

     When VALID REQUIRED calls a udf that does a GET and then CLEAR
     GETS, dBASEWin sends the caret back to the CLEARed GETS after returning
     from the udf.

     USE a table and @..GET <field> PICTURE "@R (999) 999-9999" followed
     by READ, data entry is prohibited after left parenthesis 
     (If @r is used in PICTURE, a GP fault occurs).

     When browsing a .DBF with a FOR condition, appending a record will
     cause it to lose the filter.	

     APPEND FROM <SDF>, <DELIMITED>, or DELIMITED WITH <CHR> from an
     ASCII file brings in the correct number of records but the parsing
     is incorrect.  Data brought in is improperly distributed although 
     consistent for different ASCII types.  This occurs when the last field 
     is a memo.

     @..GET FUNCTION "@R" ignores the template and displays an empty GET
     field.  The PICTURE option does work.
	
     On a BROWSE, the FOR condition is evaluated twice for each record
     and three times for the first and last record.

     LOAD DLL [LoadDLL] in dBASEWIN.INI will Quit dBASE, if it fails to
     find the .DLL, or tries to load a non existent .DLL.

     SET KEY TO command does not work if a relation is active.

     PACK after a DELETE ALL with a filter active will cause a GP fault.
   
     Reindexing with a filter active will sometimes cause a crash.

     COPY TO with a Binary field does not work for dBASE and Paradox tables.

     If you don't have a printer installed, any of the printer commands or 
     functions will cause a GP fault.

     Can't resize any of the columns in the Table Structure window.

     Multi-page format file (.fmt) does not break pages correctly.  @..SAY..
     GET commands from different pages overlap each other.

     With an activate window and popup, SAVE SCREEN and then RESTORE SCREEN
     does not restore popups correctly.  Popups will remain on the screen
     when they are supposed to be gone.

     When status bar is OFF, no message will be displayed, when using 
     DEFINE MENU, DEFINE POPUP, DEFINE PAD with the MESSAGE clause.

     Defining and activating several windows within a procedure called from 
     a popup will cause a GP.  

     If a memo field is opened in a window, any get fields behind that 
     window will appear on top of the memo window.

     If a memo field is called with @...GET open window, the memo field 
     will not remain open after a clear gets.

     When exiting a memo field called from a READ statement, the focus will
     be lost and can be regained by using a mouse to click on the get 
     associated with the memo.

     Assigning DOS drivers other than ASCII to _pdriver will cause a runtime
     error.

FORM DESIGNER
     Synchronization and focus among the various Form Designer tools is 
     problematic.  The user will have to close tools manually on exiting 
     form design session.

     The MENU Designer is under construction and not ready for testing.

     In general, the WHEN property should be avoided.
	 
     The MDI is always true in the Form Designer. Other window properties of 
     FORM, such as Resizable and Minimized are also not working via the Form 
     Designer.
	 
     EDIT Controls and ENTRYFIELDs with Memo fields are unstable.
	 
     The VALUE of a horizontal scroll bar does not change at run time.
	 
     The SPEEDBAR property of Pushbutton has no effect.

     A WAIT after OPEN FORM and SET FOCUS TO <form> does not wait but will 
     display a message if the event OnGotFocus has a WAIT in it. In other 
     words, you have 2 WAIT's active with the message displayed from each 
     but only 1 key to clear.

     ONCLOSE event handler is called when <ESC> closes the form, but not
     when  closeform() is called to close the form.   Closing the form from 
     the control menu also fails to call OnClose

     Reassigning the OnSelection several times in a class of FORM can
     cause a  GPF.

     There is no OLE control in the Form Designer control palette.

     When custom controls from a procedure file are added to a form
     through the Form Designer, the generated code doesn't include a
     SET PROCEDURE TO that procedure file.
	 
     View property does not respect full directory path filename.

     CTRL+W or <File><Save & Close> will cause a GP in the Procedure Editor
     if you have made a change to the current procedure (verify = yellow).

     Relationships between tables in a browse object are not maintained by
     the browse object.
     
     Form.OnLostFocus events can crash the Form Designer when another
     control is on the form.

     Bitmap properties on pushbuttons cannot be assigned bitmap files yet.

     VALID procedure should be used with caution.  

     Can't use a .dbf view with the Forms Expert.

PARADOX
     To use Paradox tables in multi-user mode, SET REFRESH TO a
     non-zero value.  
     
     Index ON will overwrite existing tags without warning (even
     when SET SAFETY is ON).  With DELETE TAG <tagname>,
     Secondary index tags should be deleted first (before
     Primary).  Following DELETE TAG (which deletes the Primary
     index) the table should be closed and re-USEd.
     
     The Create an Expression dialog doesn't insert the necessary
     colon delimiters for field names which contain spaces or
     other special characters.
     
     You cannot delete a Primary index via the Table|Table
     Utilities|Manage Index Tags dialog.
     
     SET ORDER TO <Secondary Index Tag> cancel an SET FILTER.
     
     Some minor problems that might occur immediately following
     the creation of a Secondary index can be avoided.  After
     creating the Secondary index, close, and then re-USE the
     table, and specify the Secondary index with SET ORDER TO.
     
     Append From <Paradox Table> For <condition>, when source
     table includes a numeric field, may trigger errors and may
     not append data in all fields.

CODE BLOCK
     Executing a code block containing a condition {LOCATE}{LIST FOR}
     {;COUNT FOR ...} and even {;SET FILTER TO ...} will cause a GP Fault.
     
     Code blocks cannot currently contain nested braces. That is, you 
     cannot place date literals, key labels or code blocks inside 
     a code block.  For example: 
		    mycode = {;bday = {10/30/67}} doesn't work.

REPORTS
     CREATE REPORT/MODI REPORT does nothing when Crystal Reports is
     still  active.

     Cannot select a Paradox table inside Crystal. You'll get the error: 
     "Error recognizing file".

     Cannot delete Record Selection Formula in Crystal.

     If you want to run Crystal Report's Personal Trainer, you must have
     your current directory set to where you installed dBASEWin.

IDAPI
     Executing the IDAPI Configuration Utility (Idapicfg.exe) on any system
     with a display resolution of 800 x 600 or greater will encounter display
     problems.

SAMPLES
     Executing samples under low resources (about 50% free) may cause
     instability.

