fuzzyocelot
Programmer
Hi everyone!
I have a bit of a mystery on my hands, and I hope someone may be able to help me figure it out. This particular mystery involves an Access 2002 SP3 front end with a SQL Server 2000 SP3a back end. I also tried this with a SQL Server 2005 SP2 back end. The operating system the Access front end is running on is Windows XP Professional 2002 SP2. SQL Server is running on Windows Server 2003 SP2.
I wasn’t sure if I should post this in the Access forum or SQL Server. I apologize if this isn’t the right forum. I originally posted this in an Access forum but haven’t had a lot of luck there yet. So I thought I’d try a SQL Server forum. This is going to be a large post. I hope no one minds.
Anyway, I am a former programmer turned SQL Server DBA about 6 months ago. Every day I check the SQL Server error logs. For the last couple of days we’ve noticed that a particular SQL login keeps failing. Some days it fails 20 to 30 times. That’s how we noticed it. It’s called “Admin” and it’s only used for one SQL database. I’ll call it DatabaseA. The person who owns this database said only two people know the password for that particular login and they haven’t been using it lately. So I started a SQL Trace in order to try and figure out who is using this login or at least what their computer name or IP address is. In the trace, we noticed the hostname was either the generic/default computer name we use at my work place or it was the web portal server name. Which means we can’t track the SQL login failure to any particular computer or person.
When I ran the trace the next day, I noticed an actual computer name appeared with the admin login failure. So I did some look-ups and was able to determine that computer name belonged to one of my co-workers! So I “interrogated” her about it. She’s a great person and a friend so I had to give her a hard time about it, jokingly of course. It turns out that there was a certain MS Access mdb that one of her clients was having a problem with and she ran it this morning. It wasn’t returning the correct data. The back end is the same SQL Server but a different database. I’ll call it DatabaseB. I obtained a copy of the mdb and ran it myself. It prompted me for a database login and password, which I entered. This login isn’t remotely related to the admin login, by the way. The ODBC connection for this mdb is set up correctly on my computer. I know because I’ve used it many times without problem. In this instance, it defaulted to the correct login so I typed in the correct password. It was accepted. No errors. So then I checked the SQL trace. Sure enough! My friend’s computer name showed up! She wasn’t even at her computer so I know it was because I ran it. I figured out why it shows her computer name and not mine. I think that’s a separate issue which I won’t cover here.
Anyway, for giggles I created a new blank Access mdb. It contained absolutely nothing. Then I linked to a table in the same SQL database (DatabaseB) my friend was using with the same ODBC connection. I linked to a table and clicked the OK button. I did not show up in the trace. Then I closed Access completely, opened up the new mdb I had created, and opened the linked table. It prompted me for the correct login information. I entered the password, clicked okay, and it opened the table. Guess what? I showed up in the trace results (my computer name showed up)! How weird is that?![[ponder]](/data/assets/smilies/ponder.gif "[ponder] [ponder]")
Does anyone have any ideas why this is happening and how to fix it?
Following is a summary of the things I’ve tried with no success:
[ol]
[li]The admin login is a userid for DatabaseA. We’re not currently using Windows domain security at this point and it’s not my call to switch. Also, DatabaseA was created by a vendor along with it’s application. I can’t change the login to something else. Besides, the more I think about this the more I feel it has absolutely nothing to do with DatabaseA and it’s Admin login. I dropped this login from our development server and I got the exact same results as before.[/li]
[li]The Admin user only has rights to DatabaseA and has no rights to any of the other databases. The login I was using to connect to DatabaseB has read-only rights to DatabaseB and has no rights on any other database. [/li]
[li]I’ve tried this whole thing connected to a remote 2000 database (development and production), a remote 2005 database (development; we’re upgrading), a local 2000 database, and a local 2005 database. I get the same results every time. By local, I mean my computer. When I saw the same error message in the 2005 SQL logs, it showed my IP address and “Error: 18456, Severity: 14, State: 5”. [/li]
[li]I tried it with DatabaseC, and the exact same login failure message showed up in the SQL Server error log. [/li]
[li]These databases are not related in any way, shape, or form. They are completely different and separate from each other. [/li]
[li]These logins I'm using have read-only access to their corresponding databases and don't exist as users in other databases. [/li]
[/ol]
ODBC connection setup:
[ol]
[li]I went to the Control Panel and used “Data Sources (ODBC)”. [/li]
[li]Then I went to the System DSN tab. [/li]
[li]I click the Add button. [/li]
[li]I select the SQL Server driver. [/li]
[li]I enter a name such as “TestDSN”. [/li]
[li]I enter the server name such as “ProdSQL”. [/li]
[li]I click the Next button. [/li]
[li]I select “With SQL Server authentication using a login ID and password entered by the user”. [/li]
[li]I enter the user name and password such as “TestUser” and “test1234”. [/li]
[li]I leave the Client Configuration button alone. (FYI: The network library selected is TCP/IP and the port is determined dynamically. The server name is correct.) [/li]
[li]I click the Next button. [/li]
[li]I change the default database to DatabaseB or DatabaseC. I’ve tried both. I have also checked the drop down list and the one database associated with the login I used is there. No other database is listed. [/li]
[li]I leave everything else as the default. (“Use ANSI quoted identifiers” and “Use ANSI nulls, paddings and warnings” are both checked) [/li]
[li]I click the Next button. [/li]
[li]I leave everything else as the default. (“Perform translation for character data” is checked) [/li]
[li]I click the Finish button. [/li]
[li]I click the Test Data Source button and it’s successful.[/li]
[/ol]
Could it have something to do with the driver? According to the ODBC Data Source Administrator, the driver version is 2000.85.1117.00.
I would GREATLY appreciate any suggestions before I got even more insane!![[dazed]](/data/assets/smilies/dazed.gif "[dazed] [dazed]")
I did an ODBC trace and have a log file. Below is part of the log file. I didn’t want to post the whole thing because it’s pretty large.
I have a bit of a mystery on my hands, and I hope someone may be able to help me figure it out. This particular mystery involves an Access 2002 SP3 front end with a SQL Server 2000 SP3a back end. I also tried this with a SQL Server 2005 SP2 back end. The operating system the Access front end is running on is Windows XP Professional 2002 SP2. SQL Server is running on Windows Server 2003 SP2.
I wasn’t sure if I should post this in the Access forum or SQL Server. I apologize if this isn’t the right forum. I originally posted this in an Access forum but haven’t had a lot of luck there yet. So I thought I’d try a SQL Server forum. This is going to be a large post. I hope no one minds.
Anyway, I am a former programmer turned SQL Server DBA about 6 months ago. Every day I check the SQL Server error logs. For the last couple of days we’ve noticed that a particular SQL login keeps failing. Some days it fails 20 to 30 times. That’s how we noticed it. It’s called “Admin” and it’s only used for one SQL database. I’ll call it DatabaseA. The person who owns this database said only two people know the password for that particular login and they haven’t been using it lately. So I started a SQL Trace in order to try and figure out who is using this login or at least what their computer name or IP address is. In the trace, we noticed the hostname was either the generic/default computer name we use at my work place or it was the web portal server name. Which means we can’t track the SQL login failure to any particular computer or person.
When I ran the trace the next day, I noticed an actual computer name appeared with the admin login failure. So I did some look-ups and was able to determine that computer name belonged to one of my co-workers! So I “interrogated” her about it. She’s a great person and a friend so I had to give her a hard time about it, jokingly of course. It turns out that there was a certain MS Access mdb that one of her clients was having a problem with and she ran it this morning. It wasn’t returning the correct data. The back end is the same SQL Server but a different database. I’ll call it DatabaseB. I obtained a copy of the mdb and ran it myself. It prompted me for a database login and password, which I entered. This login isn’t remotely related to the admin login, by the way. The ODBC connection for this mdb is set up correctly on my computer. I know because I’ve used it many times without problem. In this instance, it defaulted to the correct login so I typed in the correct password. It was accepted. No errors. So then I checked the SQL trace. Sure enough! My friend’s computer name showed up! She wasn’t even at her computer so I know it was because I ran it. I figured out why it shows her computer name and not mine. I think that’s a separate issue which I won’t cover here.
Anyway, for giggles I created a new blank Access mdb. It contained absolutely nothing. Then I linked to a table in the same SQL database (DatabaseB) my friend was using with the same ODBC connection. I linked to a table and clicked the OK button. I did not show up in the trace. Then I closed Access completely, opened up the new mdb I had created, and opened the linked table. It prompted me for the correct login information. I entered the password, clicked okay, and it opened the table. Guess what? I showed up in the trace results (my computer name showed up)! How weird is that?
Does anyone have any ideas why this is happening and how to fix it?
Following is a summary of the things I’ve tried with no success:
[ol]
[li]The admin login is a userid for DatabaseA. We’re not currently using Windows domain security at this point and it’s not my call to switch. Also, DatabaseA was created by a vendor along with it’s application. I can’t change the login to something else. Besides, the more I think about this the more I feel it has absolutely nothing to do with DatabaseA and it’s Admin login. I dropped this login from our development server and I got the exact same results as before.[/li]
[li]The Admin user only has rights to DatabaseA and has no rights to any of the other databases. The login I was using to connect to DatabaseB has read-only rights to DatabaseB and has no rights on any other database. [/li]
[li]I’ve tried this whole thing connected to a remote 2000 database (development and production), a remote 2005 database (development; we’re upgrading), a local 2000 database, and a local 2005 database. I get the same results every time. By local, I mean my computer. When I saw the same error message in the 2005 SQL logs, it showed my IP address and “Error: 18456, Severity: 14, State: 5”. [/li]
[li]I tried it with DatabaseC, and the exact same login failure message showed up in the SQL Server error log. [/li]
[li]These databases are not related in any way, shape, or form. They are completely different and separate from each other. [/li]
[li]These logins I'm using have read-only access to their corresponding databases and don't exist as users in other databases. [/li]
[/ol]
ODBC connection setup:
[ol]
[li]I went to the Control Panel and used “Data Sources (ODBC)”. [/li]
[li]Then I went to the System DSN tab. [/li]
[li]I click the Add button. [/li]
[li]I select the SQL Server driver. [/li]
[li]I enter a name such as “TestDSN”. [/li]
[li]I enter the server name such as “ProdSQL”. [/li]
[li]I click the Next button. [/li]
[li]I select “With SQL Server authentication using a login ID and password entered by the user”. [/li]
[li]I enter the user name and password such as “TestUser” and “test1234”. [/li]
[li]I leave the Client Configuration button alone. (FYI: The network library selected is TCP/IP and the port is determined dynamically. The server name is correct.) [/li]
[li]I click the Next button. [/li]
[li]I change the default database to DatabaseB or DatabaseC. I’ve tried both. I have also checked the drop down list and the one database associated with the login I used is there. No other database is listed. [/li]
[li]I leave everything else as the default. (“Use ANSI quoted identifiers” and “Use ANSI nulls, paddings and warnings” are both checked) [/li]
[li]I click the Next button. [/li]
[li]I leave everything else as the default. (“Perform translation for character data” is checked) [/li]
[li]I click the Finish button. [/li]
[li]I click the Test Data Source button and it’s successful.[/li]
[/ol]
Could it have something to do with the driver? According to the ODBC Data Source Administrator, the driver version is 2000.85.1117.00.
I would GREATLY appreciate any suggestions before I got even more insane!
I did an ODBC trace and have a log file. Below is part of the log file. I didn’t want to post the whole thing because it’s pretty large.
Code:
db3 e78-ee4 ENTER SQLAllocEnv
HENV * 0013C458
db3 e78-ee4 EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x0013C458 ( 0x083a1788)
db3 e78-ee4 ENTER SQLAllocConnect
HENV 083A1788
HDBC * 0013C464
db3 e78-ee4 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 083A1788
HDBC * 0x0013C464 ( 0x083a1830)
db3 e78-ee4 ENTER SQLSetConnectOption
HDBC 083A1830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014
db3 e78-ee4 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 083A1830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014 (BADMEM)
db3 e78-ee4 ENTER SQLSetConnectAttrW
SQLHDBC 083A1830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
db3 e78-ee4 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 083A1830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
db3 e78-ee4 ENTER SQLDriverConnectW
HDBC 083A1830
HWND 00280736
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
db3 e78-ee4 EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
HDBC 083A1830
HWND 00280736
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'Admin'. (18456)
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
db3 e78-ee4 ENTER SQLErrorW
HENV 083A1788
HDBC 083A1830
HSTMT 00000000
WCHAR * 0x0013C320 (NYI)
SDWORD * 0x0013C36C
WCHAR * 0x02A7DB28
SWORD 4095
SWORD * 0x0013C358
db3 e78-ee4 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 083A1788
HDBC 083A1830
HSTMT 00000000
WCHAR * 0x0013C320 (NYI)
SDWORD * 0x0013C36C (18456)
WCHAR * 0x02A7DB28 [ 77] "[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'Admin'."
SWORD 4095
SWORD * 0x0013C358 (77)
db3 e78-ee4 ENTER SQLErrorW
HENV 083A1788
HDBC 083A1830
HSTMT 00000000
WCHAR * 0x0013C320 (NYI)
SDWORD * 0x0013C36C
WCHAR * 0x02A7DBDC
SWORD 4005
SWORD * 0x0013C358
db3 e78-ee4 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 083A1788
HDBC 083A1830
HSTMT 00000000
WCHAR * 0x0013C320 (NYI)
SDWORD * 0x0013C36C (0)
WCHAR * 0x02A7DBDC [ 66] "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed"
SWORD 4005
SWORD * 0x0013C358 (66)
db3 e78-ee4 ENTER SQLErrorW
HENV 083A1788
HDBC 083A1830
HSTMT 00000000
WCHAR * 0x0013C320 (NYI)
SDWORD * 0x0013C36C
WCHAR * 0x02A7DC72
SWORD 3930
SWORD * 0x0013C358
db3 e78-ee4 EXIT SQLErrorW with return code 100 (SQL_NO_DATA_FOUND)
HENV 083A1788
HDBC 083A1830
HSTMT 00000000
WCHAR * 0x0013C320 (NYI)
SDWORD * 0x0013C36C
WCHAR * 0x02A7DC72
SWORD 3930
SWORD * 0x0013C358
db3 e78-ee4 ENTER SQLFreeConnect
HDBC 083A1830
db3 e78-ee4 EXIT SQLFreeConnect with return code 0 (SQL_SUCCESS)
HDBC 083A1830
db3 e78-ee4 ENTER SQLAllocConnect
HENV 083A1788
HDBC * 0013C464
db3 e78-ee4 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 083A1788
HDBC * 0x0013C464 ( 0x083a1830)
db3 e78-ee4 ENTER SQLSetConnectOption
HDBC 083A1830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014
db3 e78-ee4 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 083A1830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014 (BADMEM)
db3 e78-ee4 ENTER SQLSetConnectAttrW
SQLHDBC 083A1830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
db3 e78-ee4 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 083A1830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
db3 e78-ee4 ENTER SQLDriverConnectW
HDBC 083A1830
HWND 00280736
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
db3 e78-ee4 EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 083A1830
HWND 00280736
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'PropertyAppraiser'. (5701)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english. (5703)
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0013C488
SWORD 2
SWORD * 0x0013C480
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0013C488 (2)
SWORD 2
SWORD * 0x0013C480 (2)
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0013C398
SWORD 200
SWORD * 0x0013C480
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0013C398 [ 24] "SQLSRV32.DLL"
SWORD 200
SWORD * 0x0013C480 (24)
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0013C362
SWORD 2
SWORD * 0x0013BF34
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0013C362 (2)
SWORD 2
SWORD * 0x0013BF34 (2)
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x02A7FB60
SWORD 2
SWORD * 0x0013BF34
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x02A7FB60 (1)
SWORD 2
SWORD * 0x0013BF34 (2)
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x02A7FB62
SWORD 2
SWORD * 0x0013BF34
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x02A7FB62 (1)
SWORD 2
SWORD * 0x0013BF34 (2)
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0013C368
SWORD 2
SWORD * 0x0013C34E
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0013C368 (1)
SWORD 2
SWORD * 0x0013C34E (2)
db3 e78-ee4 ENTER SQLSetConnectOption
HDBC 083A1830
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001
db3 e78-ee4 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 083A1830
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001 (BADMEM)
db3 e78-ee4 ENTER SQLAllocStmt
HDBC 083A1830
HSTMT * 0013BF2C
db3 e78-ee4 EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 083A1830
HSTMT * 0x0013BF2C ( 0x083a2770)
db3 e78-ee4 ENTER SQLGetStmtOption
HSTMT 083A2770
UWORD 0
PTR 0x0013BED8
db3 e78-ee4 EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 083A2770
UWORD 0
PTR 0x0013BED8
db3 e78-ee4 ENTER SQLSetStmtOption
HSTMT 083A2770
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
db3 e78-ee4 EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 083A2770
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
db3 e78-ee4 ENTER SQLExecDirectW
HSTMT 083A2770
WCHAR * 0x1B074BB8 [ -3] "SELECT Config, nValue FROM MSysConf\ 0"
SDWORD -3
db3 e78-ee4 EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 083A2770
WCHAR * 0x1B074BB8 [ -3] "SELECT Config, nValue FROM MSysConf\ 0"
SDWORD -3
DIAG [S0002] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'MSysConf'. (208)
db3 e78-ee4 ENTER SQLErrorW
HENV 083A1788
HDBC 083A1830
HSTMT 083A2770
WCHAR * 0x0013BE6C (NYI)
SDWORD * 0x0013BEB8
WCHAR * 0x02A7DB28
SWORD 4095
SWORD * 0x0013BEA4
db3 e78-ee4 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 083A1788
HDBC 083A1830
HSTMT 083A2770
WCHAR * 0x0013BE6C (NYI)
SDWORD * 0x0013BEB8 (208)
WCHAR * 0x02A7DB28 [ 78] "[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'MSysConf'."
SWORD 4095
SWORD * 0x0013BEA4 (78)
db3 e78-ee4 ENTER SQLErrorW
HENV 083A1788
HDBC 083A1830
HSTMT 083A2770
WCHAR * 0x0013BE6C (NYI)
SDWORD * 0x0013BEB8
WCHAR * 0x02A7DBDA
SWORD 4006
SWORD * 0x0013BEA4
db3 e78-ee4 EXIT SQLErrorW with return code 100 (SQL_NO_DATA_FOUND)
HENV 083A1788
HDBC 083A1830
HSTMT 083A2770
WCHAR * 0x0013BE6C (NYI)
SDWORD * 0x0013BEB8
WCHAR * 0x02A7DBDA
SWORD 4006
SWORD * 0x0013BEA4
db3 e78-ee4 ENTER SQLFreeStmt
HSTMT 083A2770
UWORD 1 <SQL_DROP>
db3 e78-ee4 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 083A2770
UWORD 1 <SQL_DROP>
db3 e78-ee4 ENTER SQLGetInfoW
HDBC 083A1830
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0013CC04
SWORD 200
SWORD * 0x0013CCCE
db3 e78-ee4 EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 083A1830
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0013CC04 [ 40] "Microsoft SQL Server"
SWORD 200
SWORD * 0x0013CCCE (40)
db3 e78-ee4 ENTER SQLAllocStmt
HDBC 083A1830
HSTMT * 08646434
db3 e78-ee4 EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 083A1830
HSTMT * 0x08646434 ( 0x083a2770)
db3 e78-ee4 ENTER SQLGetStmtOption
HSTMT 083A2770
UWORD 0
PTR 0x0013CC54
db3 e78-ee4 EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 083A2770
UWORD 0
PTR 0x0013CC54
db3 e78-ee4 ENTER SQLSetStmtOption
HSTMT 083A2770
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
db3 e78-ee4 EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 083A2770
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)![[noevil]](/data/assets/smilies/noevil.gif "[noevil] [noevil]")
On the other hand, it sucks that someone else is having to deal with this "pain"! If we figure it out, I'll be sure to post it.