ID: Q115772
2.60 | 2.60
The information in this article applies to:
Below is the complete FoxPro Connectivity Kit for Windows and MS-DOS CKREADME.TXT file. This file is found on Disk 1 of the Connectivity Kit.
CKREADME.TXT
Microsoft(R) FoxPro(R) Version 2.6 Professional Edition
Connectivity Kit for Windows(TM) and MS-DOS(R)
(C)1994 Microsoft Corporation. All Rights Reserved.
CONTENTS
Part Description ---- -----------
1 Installation
2 Tips and Tricks
3 Changes to Connectivity Kit User's Guide Since Printing
4 Answers to Commonly Asked Questions
Part 1: Installation
Distribution Kit Connectivity Kit Library Construction Kit WorkGroup Extensions (FoxPro for Windows only)
To install the Professional Edition of FoxPro, first install the main FoxPro product, then follow the installation instructions included with each individual kit. The order in which the kits are installed does not matter.
1. Replace the following files, located in the subdirectory
WIZARDS, with the versions shipped with the Professional
Edition.
WIZARD.APP
WZ_BQUER.APP
WIZARDS.
WIZARD.DBF
WIZARD.FPT
The first time you run the Client-Server Wizard these
files are re-created with new default values.
1. Create a new directory called ODBC on your hard drive.
2. Copy the contents of the two ODBC disks into this
directory.
Part 2: Tips and Tricks
If you're using ORACLE, make sure you read the ORACLE.TXT file on the ODBC disk. This file contains information you need to make a connection to ORACLE.
You can reduce the length of the data exported from SQL Server by using the Transact-SQL command "SET TEXTSIZE n", where n is equal to the desired text size in bytes. For example, to limit the length of data to 20K, you would use the command "SET TEXTSIZE 20480". For an explanation of the SET TEXTSIZE command, refer to your SQL Server documentation.
If the data in an exported field exceeds the available memory, DB-Library will terminate the connection.
This limit does not apply to FoxPro for Windows. If you want to import a text or binary field that exceeds 65530 bytes, you can import the data into FoxPro for Windows and then use the data in FoxPro for MS-DOS.
For more information about specific messages, refer to "*Addition to the Appendix: System Warning Messages*" in Part 2, "Changes to Connectivity Kit User's Guide Since Printing."
You'll find an explanation of the more common SQL Server errors in the Microsoft SQL Server Troubleshooting Guide. If you don't find information about a specific SQL Server error message in the Troubleshooting Guide, please contact your SQL Server system administrator or your SQL Server primary support provider.
Part 3: Changes to Connectivity Kit User's Guide
Since Printing
Name Size
---- ----
CharNull 30
IntNull 20
FloatNull 20
DateNull 23
DBSetOpt(<expN>, <expC>[, <exp>]) DBGetOpt(<expN>, <expC>)
For more information of these functions see the Connectivity Kit User's Guide.
Syntax: DBError (<expN1> [, @<memvar1> [, @<memvar2>] [,<expN2>]])
<expN2> returns a value between 1 and 5 corresponding to the error message in the error message list. Invalid values for <expN2> are defaulted to the nearest valid value. If the parameter is not specified, the latest error message is returned.
The following are corrections to the documentation since printing.
Add error number 36 "Cannot set transaction option while in a transaction" (MS-DOS only).
If you are in manual transaction mode and have made the
first call to DBExec(), you are in an active
transaction. In this case, you must explicitly end the
transaction by calling DBTransact() with a Commit or
Rollback statement before you can either call
DBSetOpt() to change the transaction mode or call
DBDisconnect().
In manual mode, you can end a current transaction only by calling DBTransact(), not by changing the transaction mode with DBSetOpt(). The new description for FPSQL error 33 should read:
Before you can call DBDisconnect(), you need to end the
current transaction by calling DBTransact().
Msg System Warning Message Platform
No.
1 Failed to set connection time-out (MS-DOS/Windows)
2 Failed to set general time-out (MS-DOS/Windows)
3 Data precision lost in conversion (MS-DOS/Windows)
4 Failed to convert memo field (MS-DOS/Windows)
5 Failed to clear connection (MS-DOS/Windows)
6 Failed to set transaction mode (Windows only)
asynchronous mode (Windows only)
10 Failed to set DB-LIB text limit (MS-DOS only)
database (MS-DOS only)
Shows any data conversion error from whatever data source
type to FoxPro. This message is displayed once at the
end of the result set conversion for one or multiple
problems encountered during the conversion process.
FPSQL was unable to clear the connection. The error
could indicate corruption of FPSQL memory space or a
problem either in the connection channel or on the
data source.
Indicates any error while converting data to FoxPro
memo fields (not enough memory, temporary file error,
etc.) This message is displayed once at the end of the
result set conversion for one or multiple problems
encountered during the conversion process.
Windows only. Indicates an error in the ODBC call for
the current data source.
FPSQL was unable to set the specified connection timeout
for an attempted connection to a data source. The
connection attempt will timeout according to the data
source default connection timeout.
MS-DOS only. Shows an error in setting the maximum
DB-Library text size to 65530 bytes.
FPSQL was unable to set the specified general timeout
for a connection to a data source. The connection
will use the data source default general timeout.
MS-DOS only. Indicates an error when trying to set in
use the database specified as the fourth parameter in
DBConnect().
Windows only. Indicates an error in the ODBC call for
the current data source.
Part 4: Answers to Commonly Asked Questions
Question 1
Our organization includes several FoxPro developers. Does each developer need an individual copy of the Connectivity Kit?
Answer 1
Your organization must own one licensed copy of the Connectivity Kit per developer, for each developer creating applications that use the Connectivity Kit. If five developers in your organization create applications using one or both of the Connectivity Kit libraries (FPSQL.PLB and/or FPSQL.FLL), you must own five licensed copies of the Connectivity Kit.
Question 2
I own licensed copies of both the FoxPro Distribution Kit and the FoxPro Connectivity Kit. May I distribute the FPSQL libraries with applications I develop using the Distribution Kit?
Answer 2
Yes. As a licensed user of both the FoxPro Distribution Kit and the Connectivity Kit, you are free to distribute the FPSQL.PLB and/or FPSQL.FLL library file(s) with your distributed application(s).
===================
END OF CKREADME.TXT
===================
Keywords : kbsetup FxotherReadme
Version : 2.60 | 2.60
Platform : MS-DOS WINDOWSLast Reviewed: May 22, 1998