User bio
404 bio not found
Member since Dec 29, 2022
Replies:

The client was upgraded to the 2018.1.3.414 ODBC Driver to resolve other ODBC issues they were having.  We've obtained an ODBC log from them and the indices are shown being passed as part of the table definition as a whole, but prior to that inside the ODBC log is this:

--> SQLFreeStmt: (09:24:33:669) hstmt = 0x0732cfa0 option = 1
>> Sent: (09:24:33:669)
  0000:  00 00 00 00 04 00 00 00 01 00 00 00 43 55            ............CU
<-- SQLFreeStmt: (09:24:33:669) Returning 0

--> SQLSetConnectOptionW: (09:24:33:669) hdbc = 0x07319f40 fOption = 102 vParam = 1
<-- SQLSetConnectOptionW: (09:24:33:669) Returning 0

--> SQLGetConnectOptionW: (09:24:33:810) hdbc = 0x072ec9b0 fOption = 109
    ERROR: SQLGetConnectOption: (09:24:33:810) Option not supported
<-- SQLGetConnectOptionW: (09:24:33:810) pvParam = 0 returning -1

--> SQLAllocStmt: (09:24:33:811) hdbc = 0x072ec9b0
<-- SQLAllocStmt: (09:24:33:811) hstmt = 0x0734f478 returning 0

--> SQLTablesW: (09:24:33:811) hstmt = 0x0734f478
    TableQualifier: %
    TableOwner: 
    TableName: 
    TableType: 
    ERROR: SQLTables: (09:24:33:811) Catalogs not supported
<-- SQLTablesW: (09:24:33:811) Returning -1

I don't have anything like this running the latest version of WinSQL in house with the same ODBC driver, so this opens the question of whether it's their version of WinSQL.

Certifications & Credly badges:
Tom has no Certifications & Credly badges yet.
Global Masters badges:
Tom has no Global Masters badges yet.
Followers:
Tom has no followers yet.
Following:
Tom has not followed anybody yet.