                           WELCOME TO BORLAND SQL LINK
                 CONNECTING TO SYBASE AND MICROSOFT SQL SERVER
                 ---------------------------------------------

This file contains important, late-breaking information about Borland 
SQL Link, including revisions to the documentation. Information in these 
files supersedes information in the Borland SQL Link documentation.


TABLE OF CONTENTS
-----------------

1. Tips for using SQL Link
2. SQL LINK documentation notes
3. ObjectPAL tips for SQL Link applications



1. TIPS FOR USING SQL LINK
--------------------------


ADJUSTING THE INIT TIMEOUT PARAMETER.  You may want to change the Init
TIMEOUT value to minimize conflicts between operations, or if you use
ObjectPAL's add() method in update mode on SYBASE tables that contain
blobs.

For best performance, determine how much time a complex query would
take to complete successfully on your network, then use the IDAPI 
Configuration Utility to set DRIVERS|SYBASE|INIT|TIMEOUT to a slightly
larger number than that.  For example, if you often run complex queries
that can take up to 120 seconds to complete, be sure to set the TIMEOUT
value to more than 120 seconds.


USING DEFAULT SYBASE DRIVER FLAGS SETTING.  If your SYBASE SQL Server 
faults while executing blob writes, check the Init DRIVER FLAGS parameter.
If DRIVER FLAGS is set to 0 (the SYBASE default):

  1.  Call SYBASE Customer Support and describe the problem, referencing
      Case #125046.

  2.  Set the DRIVER FLAGS parameter to 1.  Use this DRIVER FLAGS setting 
      until you receive the necessary software fix from SYBASE.

Setting Driver Flags to 1 will enable you to execute blob writes without
causing a server fault.  This may cause the client to receive SQL Server
timeouts during blob writes.


WORKING WITH LARGE TABLES.  If you create data entry forms on large tables
you may find some performance degradation -- particularly if the user is 
allowed to view unrestricted record sets.  The following suggestions may 
help cut down the load on your server and help optimize server performance:

-  With large data sets, it is good programming practice to write applica-
   tions which access relatively few records at a time.  One way to do this
   within a form-based application is to create forms which order the data 
   by index and set RANGE criteria to limit the record set.  This can be 
   done interactively using the ORDER/RANGE dialog, but can also be con-
   trolled by the application developer.  (For example, instead of creating
   a form which displays all orders for all customers, write your applica-
   tion to limit the user's working selection by criteria such as customer
   name, state, and area code.)

-  Applications which do more reads than updates on large data sets may
   benefit from ordering on a CLUSTERED index.

-  Clients that use Net-Library should consider adding the URGENT option to
   their server configuration string.  For further information, see 
   Appendix A of SYBASE's Installation and Reference Manual for Open Client
   Net Library for DOS (document ID#37850-01-0100-03). 




2. SQL LINK DOCUMENTATION NOTES
-------------------------------

CONFIGURING SQL Link FOR YOUR SQL SERVER's SORT ORDER. If your 
SQL Server is configured with a non-binary sort order please
call your local Borland Technical Support for a language driver
that will match your server's sort order.


MULTIPLE RESULT SETS.  SQL Link does not support the use of stored 
procedures that return multiple answer sets.


USING ALIASES WITHOUT SPECIFYING A LANGUAGE DRIVER.  If no language
driver is specified, the default language driver is ASCII.  Language-
specific processes like character translation and table name validation 
will default to U.S. rules.  For further information, see the section
on Borland language drivers in your Connecting To... manual.

   
SQL LINK USER'S GUIDE, PAGE 13.  Two additional points for the subsection
on "Using Table windows" are: (1) The .TVS file is not automatically dele-
ted when the SQL table is deleted, and (2) If you change your private dir-
ectory the table will no longer be displayed with the properties you set.


SQL LINK USER'S GUIDE, PAGE 14.  Add the following note before the para-
graph that begins with "For detailed information..."

     NOTE:  The above tables are only generated if the query is processed
            within the QBE environment.  For further information, see
            "QBE query processing," in Chapter 3.


SQL LINK USER'S GUIDE CHAPTER 4.  Chapter 4, "SQL-enabled ObjectPAL," does
not document the transactionsActive() database method or the 
update(fname,fvalue [,fname,fvalue]) tcursor method.  For information
about these two methods, see NEWPAL.DB. 


SQL LINK USER'S GUIDE, PAGE 29.  The description of the syntax for 
beginTransaction includes the parameter ([const isoLevel String]).  This
parameter is not supported in this release of SQL Link.


SQL LINK USER's GUIDE, PAGES 29 - 31.  Tables 4.5 and 4.6 are not sorted
by object type.

SQL LINK USER'S GUIDE, PAGE 30.  Table 4.5, "Standard ObjectPAL methods
that support SQL Link," includes the sort table method.  The sort method
belongs in Table 4.6, "Standard ObjectPAL methods that do not support
SQL Link." 


SQL LINK USER'S GUIDE, PAGE 37.  peOptRecLockFail should be
peOptRecLockFailed. Error constant is incorrect.


SQL LINK USER'S GUIDE, PAGE 40.  The steps for rebinding forms discussed
on this page of the User's Guide should more properly be the following:

1.  Copy Paradox tables to the SQL server.

2.  Index the server tables to duplicate the linking and ordering indexes
    you had on your original tables.

3.  Before you rebind the form, copy it to a different subdirectory so that
    Paradox for Windows will not be able to find the original tables when
    you open the form.

4.  Change your working directory to the new subdirectory and Open the form
    in Design Mode.

5.  When the original Paradox tables cannot be found, you will be allowed 
    to replace those tables in the data model with the equivalent SQL 
    tables.

6.  In some cases, you may need to fix up the links between tables in the
    Data Model dialog.  To do this, simply unlink all tables and re-link
    on the appropriate indexes.

7.  Recreate all calculated fields.

8.  Update all hard-coded table names in ObjectPAL code.

9.  Save the form.


3. OBJECTPAL TIPS FOR SQL LINK APPLICATIONS
-------------------------------------------

For tips on how to create ObjectPAL applications for use in an SQL 
environment, see the text file OPALTIPS.TXT.
