Welcome to Database Desktop 5.1
                   ===============================

This file contains important information about Database Desktop that 
supplements and supersedes information in the Database Desktop 
documentation.


TABLE OF CONTENTS
-----------------
1. Installation
2. What Is Database Desktop?
3. Summary of New Features
4. Guide to the Documentation
5. Restrictions


1. INSTALLATION
---------------
The installation program installs Database Desktop. Follow the 
instructions in the README file.


2. WHAT IS DATABASE DESKTOP?
----------------------------
Database Desktop, is a separate application which  lets you work 
with tables interactively. For example, you can create, restructure, 
query, copy, rename,or delete a table. To access SQL tables 
using Database Desktop, you must also have Borland SQL Links 
installed.


3. SUMMARY OF NEW FEATURES
--------------------------
Database Desktop has been enhanced in the following ways:

- SQL access is now available for queries and table operations,
  including creating and restructuring tables.

- A Utilities menu with the following commands has been added:

  Add        	Adds the records in one table to those in another table
  Copy       	Makes a copy of a table, QBE query, or SQL statement
  Delete     	Deletes a table, QBE query, or SQL statement
  Empty      	Removes all records from a table
  Passwords  	Lets you add and remove passwords from the list of 
		passwords you have used in the current session
  Rename     	Changes the name of a table, QBE query, or SQL statement
  Sort       	Sorts the data in a table
  Subtract   	Removes from one table records that exist in another.

  You can use Add, Copy, Delete, and Empty on SQL tables.

- You can execute SQL statements using the SQL Editor.


4. GUIDE TO THE DOCUMENTATION
-----------------------------
Database Desktop Online help fully documents Database Desktop.
Press F1 any time Database Desktop is running to get help. In 
addition to topic search and context sensitive help, task-oriented 
help is available for many topics. 


5. RESTRICTIONS
---------------
- You cannot copy from a Paradox table to a dBASE table if the Paradox
  table has a BYTE field. You will get the error message "Invalid field
  type." To move data from a Paradox table that has a BYTE field to the
  dBASE file format, follow these steps:

  a. Use File|New|Table to create a dBASE table.
     - Borrow the structure of the Paradox table.
     - Set the type of the BYTE field to Memo in the dBASE table.
     - Save the new table structure.

  b. Use Utilities|Add to copy the records from the Paradox table to
     the new dBASE table. The binary contents of the BYTE field will be
     stored in the corresponding Memo field.

- When you use File|New|Table to create a remote SQL table, the list of
  field types available for the server may include unsupported types.
  If you attempt to use these field types, an appropriate error message
  is displayed.

  For example, for InterBase servers, the type ARRAY appears in the
  field type list. If you attempt to create a table with an ARRAY
  field, the error message "Cannot create a field of type ARRAY" is
  displayed when you Save the table.

  This situation is most common for databases accessed using ODBC.

- When accessing tables on SQL servers, anomalies can result from
  differing table-naming conventions. When you display a list of
  tables for some servers, the tables listed include user names.
  For other servers, user names are not included.

  For example, if you choose Utilities|Copy and choose an alias for
  an InterBase server, you might see the following table list:

    CUSTOMER
    ORDER
    LINEITEM

  On a Sybase server, you might see the the user name as well (Henry
  is the user name):

    Henry.Customer
    Henry.Order
    Henry.LineItem

  When specifying table names in Database Desktop dialog boxes, follow
  the server's table-naming convention. On an InterBase server, enter
  just the table name. On a Sybase server, enter <username>.<tablename>.

  If you do not follow the server's table-naming conventions and a table
  of the specified name exists, confirmation messages may not be displayed
  when you expect to see them. In particular, if you copy to an existing
  table on a server, and you do not follow the table-naming convention of
  the server, you will not be asked whether to overwrite the existing table.

  For example, suppose your user name is Henry and a table named
  Henry.Customer exists on your Sybase server. If you choose Utilities|Copy
  to copy a local Customer table to your server and you specify
  Customer as the destination table name instead of Henry.Customer,
  the table Henry.Customer on your server is overwritten without notice.
  If, however, you specify Henry.Customer as the destination table, you
  are asked whether to overwrite the existing table.