SYBASE各类数据库访问驱动（ado,odbc,oledb）

readme.txt Sybase ASE OLE DB Provider, TDS Version Microsoft Windows 9x, NT, 2000, ME, XP Version 02.70.0032 (12.5.1/P-EBF11786 ESD#02/02.70.0032) March 2004 CONTENTS Sybase ASE OLE DB Provider, TDS Version Problems Fixed Notes and Known Problems Contacting Sybase Technical Support Installed Files Sybase ASE OLE DB Provider, TDS Version The Sybase ASE OLE DB Provider connects an ADO-based application to Sybase ASE 11.X, 12.X. The Sybase ASE OLE DB Provider is supported on current and recent 32-bit Windows operating systems Windows 9x, Windows NT 4.0 and Windows 2000. IMPORTANT: You must have at least version 2.60 of the Microsoft Data Access Components (MDAC) installed to use the Sybase ASE OLE DB Provider 2.70.0032. The current version at the time of DataDirect Technologies's original release was 2.7. You can download a utility that determines the version of your currently installed MDAC from the following Microsoft site: http://www.microsoft.com/data/download.htm#CCinfo You can download the latest MDAC from the Microsoft site: http://www.microsoft.com/data If you are using MDAC 2.10 and MDAC 2.50, and encounter problems, please upgrade to the current MDAC level and test for resolution. If problem persists please contact Sybase Technical Support. IMPORTANT NOTE: Sybase ASE OLE DB Provider now supports ASE/DTM. Please read the special note below for information regarding a known issue with the use of MTS/DTC. You must have the license for ASE/DTM in order to utilize this capability, with the latest ASE 12.0/12.5 release. ********************************************************************* *** PLEASE NOTE - The following is a known issue, and has been *** *** addressed by the following Sybase ASE releases: *** *** *** *** Sybase ASE 12.0.0.7 IR (Interim Release) *** *** Sybase ASE 12.5.0.3 IR (Interim Release) *** *** *** *** Currently, multiple components in an MTS/DTC application *** *** (using OLE-DB or ODBC via the XA interface) cannot share *** *** the same 'lock space' on ASE. These applications may hang *** *** if they have multiple components or connections attempting *** *** to access the same data simultaneously; even within a *** *** single MTS/DTC transaction. *** *** This problem does NOT affect ASE on NT using the Native-OLE *** *** distributed transaction interface, nor will it affect *** *** components that access separate data and do not need to *** *** share locks. *** *** This problem is caused by the way MTS/DTC generates XA *** *** transaction Ids and these issues are being addressed under *** *** CR 259265. *** ********************************************************************* Problems Fixed --------------------------------------------------- IMPORTANT NOTE for 12.5.1 SDK GA and 12.5 ESD#14 version: EBF 11529 ESD #14 from the 12.5.0 SDK is a newer build (2.70.0024)than the build included in the 12.5.1 GA release (2.70.0023). However, the builds are nearly identical in that they both contain the same Sybase fixes. The vendor built 2.70.0023 for the 12.5.1 GA release, and they also "rebuilt" the same code into 2.70.0024 for the 12.5.0 ESD#14 release (November 2003) to resolve specific customer issues. --------------------------------------------------- Version 02.70.0032 (12.5.1/P-EBF11786 ESD #02/02.70.0032) -------------------------------------------------- 331731: OLEDB: No cursor deallocation when ADO Recordset object is closed. Now when RecordsetObject.Close is issued the ASE cursors will be closed and deallocated. 327253: OLEDB: AddNew() not generating full INSERT statement 345019: OLEDB: OLEDB 2.70.0024 hangs when using 2 recordsets on a connection and when retrieving text data. 343643: OLEDB: Version 2.70 ignores MaxRecords property when Select Method = Cursor 347799: OLEDB: Unable to get a message returned from a raiserror. Instead a generic message is raised "An unknown error has occurred". -------------------------------------------------- Version 02.70.0028 (12.5.1/P-EBF11410 ESD #01/02.70.0028) -------------------------------------------------- CR 337422: OLEDB: Literal empty string as parameter in ADO application fails against ASE 12.0 with the error: "While reading characters from the client, the receiving buffer has been detected to be too small." This is ASE Error 4020. CR 337095: OLEDB: Precision error when stored procedure input parameter is set to Null. CR 336056: OLEDB: Initialization String is limited to 40 bytes in ASE OLE DB Configurator. Manually editting the IDS file exceeds this limitation. CR 334483: OLEDB: Error running proc:"The name 'sp_who sa' is not a valid identifier" with use of adCmdText CR 331362: OLEDB: When "set nocount on" is set, headings for empty result sets are not returned to the client. -------------------------------------------------- Version 02.70.0023 (12.5.1/P/02.70.0023) -------------------------------------------------------- CR 325895: Sybase ADO provider is corrupting datetime INOUT stored procedure parameters. CR 328613: Empty strings treated as NULLs in stored procedure parameters. CR 329073: Spaces trimmed by OLEDB Provider between stored procedure name and any arguments. CR 329429: Sybase Varchar output parameters from stored procedures are truncated at 4 bytes ------------------------------------------------------- Version 02.70.0024 (12.5.0/P-EBF11529 ESD#14/02.70.0024) -------------------------------------------------------- CR 329429: OLEDB: does not handle varbinary or varchar params longer than 255 bytes. CR 328613: OLEDB: When executing a stored procedure with an input parameter of varchar datatype, the provider wrongly passes an empty string as a NULL string to ASE. -------------------------------------------------------- Version 02.70.0022 (12.5.0/P-EBF11434 ESD#13/02.70.0022) -------------------------------------------------------- CR 320119: OLEDB: Row Cache Size is not working properly. When Sybase ASE OLE DB Provider is set to SelectMethod=0 (Cursor) only one row is fetched and the Recordset is not getting populated. Also the following error was reported: "Run-time error '3021': Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record." This has been resolved. CR 326887: OLEDB: When CursorLocation=adUseClient, an error, "-2147467259 Data provider or other service returned an E_FAIL status", occurs when select involves TEXT column. -------------------------------------------------------- Version 02.70.0020 (12.5.0/P-EBF11210 ESD#12/02.70.0020) -------------------------------------------------------- CR 314062: OLEDB: Query with Outer Joins produces error in OLEDB Provider: Syntax error at token 'ON', line 1 offset 46. CR 315113: OLEDB: INTEGER output parameter is always zero if Parameter object Size = -1 in CreateParameter. CR 313620: OLEDB: Command Timeout (oCmd.Properties.Item("Command Time Out"). Value) gives twice the expected delay. CR 315086: OLEDB: OLE-DB fails to return EED errors from stored procedures unless there is at least one result set. Instead the application gets "One of more errors occurred while processing the command" -------------------------------------------------------- Version 02.70.0016 (12.5.0/P-EBF11113 ESD#11/02.70.0016) -------------------------------------------------------- CR 300371: OLEDB: Inconsistency in setting of "Use SSL" attribute. CR 301912: OLEDB: If the OLEDB da