OLEDB驱动程序大全 Sybase-OleDB-Provider

readme.txt Sybase ASE OLE DB Provider, TDS Version Microsoft Windows 9x, NT, 2000, ME, XP Version 02.70.0023 (12.5.1/P-EBF11468/02.70.0023) September 2003 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.0016. 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 Version 02.70.0023 (12.5.1/P-EBF11468/02.70.0023) -------------------------------------------------------- 325895: OLEDB: Sybase ADO provider is corrupting datetime INOUT stored procedure parameters 328613: OLEDB: Empty strings treated as NULLs in stored procedure parameters. 329073: OLEDB: Spaces trimmed by OLEDB Provider between stored procedure name and any arguments. -------------------------------------------------------- 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 datasource does not contain the database name to connect to, and the current database to operate on is set by conn.DefaultDatabase = "dbname" then a subsequent instruction to set a parameter, cmd.Parameters.Item("@my_value").Value = <value>, resets the current database. So subsequent statements may fail because they do not exist in the database. This problem has been fixed in version 02.70.0016. CR 302579: OLEDB: When using TClientDataSet object with Delphi and OLE DB Provider there are two problems inserting data: 1. An EOLEException with message "Errors Occurred" is raised when inserting Chinese characters. 2. An EOLEException with message "Parameter data overflow for small money at ordinal 6" is raised when inserting numeric data greater than 99999, eventhough in delphi the data type is ftBCD. CR 303635: OLEDB: The OLE DB Provider was not displaying the duplicate insert error message in an ADO application. CR 306557: OLEDB: No rowcount information is returned when using clientside cursors in transactions. CR 310691: OLEDB: Using Multiple Recordsets with ADO and Sybase ASE OLE DB Provider generates: 'The Instruction at "0x100403de" referenced memory at "0x000001ec". The memory could not be "read".' This has been fixed in version 02.70.0016. --------------------------------------------------------- Version 02.70.0015 (12.5.0/P-EBF10969/02.70.0015) -------------------------------------------------- CR 294211: OLEDB: Integer Output parameter value was 0 if the size was not specified in an ADO application. CR 304000: OLEDB: Conversion errors occurred ("Parameter data overflow for smallmoney at ordinal 2") when passing large values into adCurrency parameters in an ADO application. CR 289153: OLEDB: Provider can not handle Chinese parameterized queries via Delphi 6. This is not a bug with the OLE DB Provider. The problem is caused by not explicitly setting your buffer length for the input parameter. The application was by default using a 2 byte buffer. The application will need to be modified to explicitly state the parameter size, as follows: Sql.text := ' SELECT * FROM test_emp WHERE col3 like :SNAME'; parameters.paramByName('SNAME').Size := Length(temp_s); <== this is the new line parameters.paramByName('SNAME').value := temp_s; ------------------------------------------------ Version 02.70.0012 (12.5.0/P-EBF10929/02.70.0012) ------------------------------------------------ CR 289754: OLEDB: Queries with Outer Joins under {OJ...} SQL Syntax gives SQLSTATE=42000 (Incorrect Syntax near BY) using TDS-based OLEDB driver 2.50 or above. CR 302753: OLEDB: provider hangs when executing