MTS & ADO & VB60 & INFORMIX

Hi, I'm tryng to implement a DNA architecture on an application I'm developing. The problem is that I'have found impossible to make work together Microsoft Transaction Server, ADO and Informix. I have tried with the following ODBC informix drivers with the same results (Error Message [ODBC] "Optional feature not implemented" or similar) : Informix ODBC 2.80 32 bit Informix ODBC 3.30 32 bit Intersolv 3.01 32 bit Informix Intersolv 3.11 32 bit Informix Openlink Lite for Informix 7 (32 bit) I'm using MTS 2.0, ADO 2.1, VB 6.0, Informix 7.3 Workgroup Edition and NT Server 4.0 (Service Pack 5) as OS. I have realized that my application works fine when uses Access Odbc driver, but it fails when I try to attack Informix or Sybase. I'm quite desperate, thank in advance Sent via Deja.com http://www.deja.com/ Before you buy.

triki67@my-deja.com wrote in message <7vucjn$dt4$1@nnrp1.deja.com>... > > > > Hi, I'm tryng to implement a DNA architecture on an application I'm >developing. The problem is that I'have found impossible to make work >together Microsoft Transaction Server, ADO and Informix. > > I have tried with the following ODBC informix drivers with the same >results (Error Message [ODBC] "Optional feature not implemented" or >similar) : > > Informix ODBC 2.80 32 bit > Informix ODBC 3.30 32 bit > Intersolv 3.01 32 bit Informix > Intersolv 3.11 32 bit Informix > Openlink Lite for Informix 7 (32 bit) > > I'm using MTS 2.0, ADO 2.1, VB 6.0, Informix 7.3 Workgroup Edition and >NT Server 4.0 (Service Pack 5) as OS. > > I have realized that my application works fine when uses Access Odbc >driver, but it fails when I try to attack Informix or Sybase. > > I'm quite desperate, thank in advance I am using the Informix ODBC 3.30 32 bit driver successfully with MTS and ADODB 2.1 on a WINNT 4 platform, Informix DB on a UNIX machine. Heres how I get a connection Public Function OpenNewConnection() As ADODB.Connection On Error GoTo ErrorHandler Dim NewConn As ADODB.Connection CheckState "OpenNewConnection" Set NewConn = New ADODB.Connection NewConn.Open GetConnectionString(GetDBKernel) NewConn.Execute "SET ISOLATION TO DIRTY READ" Set OpenNewConnection = NewConn Exit Function ErrorHandler: Set OpenNewConnection = Nothing Err.Raise Err.Number, Err.Source, RTErr.Description(TypeName(Me), "OpenNewConnection", Err.Description) End Function Public Function GetConnectionString(ByVal database_logical_name As String) As String On Error GoTo ErrorHandler Dim data_source_name As String CheckState "GetConnectionString" data_source_name = database_names.GetPhysicalName(database_logical_name) If officerlogin = "" Then GetConnectionString = "uid=" & rootlogin & ";pwd=" & rootpassword & ";dsn=" & data_source_name Else If officerlogin = rootlogin Then GetConnectionString = "uid=" & rootlogin & ";pwd=" & rootpassword & ";dsn=" & data_source_name Else GetConnectionString = "uid=" & officerlogin & ";pwd=" & unixpassword & ";dsn=" & data_source_name End If End If Exit Function ErrorHandler: GetConnectionString = "" Err.Raise Err.Number, Err.Source, RTErr.Description(TypeName(Me), "GetConnectionString", Err.Description) End Function The thing seems to work all right for Commit and Roll back, however there are bugs in the ODBC driver: so far I can cite the following.. 1. The AddChunk method of the ADODB.RecordSet does not work on TEXT DB fields (Informix informs that this will be corrected by mid October, still no news) 2. The MaxRecords property of the ADODB.RecordSet does not work. Hope this helps you