You’re offline. This is a read only version of the page.
From time to time I run into a problem with our SDK developed programs where there get the sqlodbc.err from one or more workstations but those workstations can run standard SL programs just fine. I understand that SDK developed programs communicate with the SQL database somewhat differently than standard SL programs but I have never figured out the cause of the sqlodbc.err issue. Sometimes restarting the SQL Browser on the server will resolve the issue but I was curious if anyone had determined more details on what causes this issue and whether there is anything that can be added/modified in an SDK developed program to avoid this issue.
*This post is locked for comments
I have the same question (0)Rick,
Thank you for posting this question to the forum. I have not seen this often, but one thing to also close SL, delete any ODBC connections (System or User; 32 or 64 bit), then launch SL again and run a report to re-create them. I have seen where a Windows Update will update the OS ODBC driver, but these connections will hold old properties or configurations. When delete and re-created they take on the newer information from the update.
I wish there was more detail on this functionality, but it is all stored in the SWIMAPI file for SL and proprietary. So there are no design docs or resources that provide how this all connects and works.
Thank you,
Carolyn
MSDSL Technical Support
Share
Report
All responses (
Answers (
4,710
