🚀 go-pugleaf

Hallo,

I'm using c++ builder with ADODB vcl unit from Borland

I got "unspecified error" running this query:

sql = " {call ReadMeasureData( 57223, 67, 279, {resultset 0,
result_set_arg})}  "

note that VBA excel code referencing ADO 2.7 com objects works well:
------------- Excel VBA code -------------------

sql = " {call ReadMeasureData( 57223, 67, 279, {resultset 0,
result_set_arg})}  "
'm_Connection.Properties("PLSQLRSet") = True 'only for oracle oledb not
required by msdaora
runSQL = sql
m_rsBrand.CursorLocation = adUseServer 'adUseClient ' adUseServer
m_rsBrand.Open runSQL, m_Connection, adOpenForwardOnly, adLockReadOnly,
adCmdText
---------------------------------------------------

After in my C++ builder application I start debug session with VCL debug,
I got Com exception in:

---------- VCL Unit ADODB ---------------------
    Recordset.Open(Source, ActiveConnection,
      CursorTypeValues[FCursorType], LockTypeValues[FLockType],
      Integer(CommandTypeValues[CommandType]) +
ExecuteOptionsToOrd(ExecuteOptions));
-----------------------------------------------

with evaluate/inspect I got:
    FCursorType = adOpenForwardOnly
    FLockType = adLockReadOnly
    CommandType = adCmdText
    ExecuteOptions = '\0' // empty


Recordset cannot be depth inspected because is COM intf
How can I discover which COM typelib is binded to this intf ?

Is it possible that ADODB unit is referencing some old ADO GUUID (2.0, 2.1,
2.5, 2.5 sp1) instead of 2.7
I know that ResultSet with MSDAORA works well only from 2.5


Should I avoid original VCL adodb unit for some thirty part Delphi ADO
wrapper ?

Thanx a lot

--
Scaravaggi Diego  T X T  e - s o l u t i o n s
work: +390225771249 mobile: +393485266985
work address: office 305 via Frigia, 27 20126 Milano (MI) Italy
Milano - Barcelona - Frankfurt - London - Paris