Missing Features There are still a few features and function calls missing from the driver, but they should not affect most environments. NET garbage collector thread finalizes these objects. Failure to do so can cause major failures in the driver due to the resources and handles being freed up re-entrantly when the. Also, since the ODBC.NET data provider is accessing and using unmanaged resources and handles in the ODBC driver during operation, you should always call the Dispose method for any ODBCConnection, ODBCCommand, ODBCCommandBuilder, or ODBCDataAdapter objects when you are done using them (deterministic destruction). NET application (VB.NET, ASP.NET, C#, Delphi.NET, Chrome). The bridge driver does not function correctly in most cases.Ģ002 and later It is recommended that you only use the ODBC.NET data provider with any.
The bridge driver does not function correctly in most cases.Ħ and later It is recommended that you only use the ODBCDirect functionality in VB 6 and not the ADO->OLEDB->ODBC bridge driver through the ADO functionality. Serverside cursors do not work properly since the OLE layer deems dynamic cursors as not being capable of handling bookmark operations, even though such cursors can handle bookmark operations in ElevateDB.ĥ and later It is recommended that you only use the ODBCDirect functionality in ASP and not the ADO->OLEDB->ODBC bridge driver through the ADO functionality. We have tested the driver successfully with Microsoft Data Access Components (MDAC) version 2.7 or higher and the following applications:Ģ000 and later Microsoft Access has problems with using an auto-increment field as part of the primary index since the Jet engine cannot "discover" the keys properly when they are not populated explicitly by the client application.ĥ.01 and later With the BDE there are problems with using an autoincrement field as part of the primary index since the BDE cannot "discover" the keys properly when they are not populated explicitly by the client application.ĭelphi 5 or later Only use a CursorLocation property of clUseClient. ElevateDB Version 2 Data Access Components Manual Table Of Contents Chapter 1 - Using the ODBC Driverģ.23 EDBYearMonthIntervalType EnumerationĪppendix A - Error Codes and Messages Appendix B - System CapacitiesĬhapter 1 Using the ODBC Driver 1.1 Application Compatibility Supported Applications The ElevateDB ODBC driver is an ODBC level 3 driver.
0 kommentar(er)
