I have some very old code that has worked for years (originally written for Sybase ASA 7) but has stopped working since I upgraded from ASA 17 (build 1358) to ASA 17 (build 2053).
We use ADO 2.5 and the Sybase ASA 17 ODBC driver and this is VB6.
Set cmdStoredProc = New ADODB.Command cmdStoredProc.CommandType = adCmdStoredProc
'Open a connection Set cmdStoredProc.ActiveConnection = dePNUIT.conApollo 'linked to s sybase 17 asa ODBC dsn cmdStoredProc.CommandTimeout = 0
'We set the stored procedure we are going to use cmdStoredProc.CommandText = "sp_insert_table_A"
'And try and loop through the parameters For intParam = 0 To cmdStoredProc.Parameters.Count - 1
...But this now fails and it returns cmdStoredProc.Parameters.Count = 0
It does not return a parameter list and any attempt to assign to a parameter fails as it says the parameter cannot be found.
I tried upgrading to ADO 2.7 as per the documentation, but this failed too.
Is this still supported?
asked 21 Jun '16, 10:23
There is a regression in one of the schema queries that the 17.0.4 ODBC driver issues. "PROCEDURE_OWNER" is a column name used when running in ODBC 2.0 mode. This column name conflicts with the PROCEDURE_OWNER special value that was introduced in 17.0.0. The quoting of the column name was inadvertently removed in 17.0.4 (17.0 build 2000).
A fix will be forthcoming.
A work-around is to revert to the older 17.0.0 ODBC driver.