Wierd behavior on querie results, on diferents computers...
-
Hi, i build a personal tool to help me in my job, i have being using it for almost a year with no issues, last month it start returning empty cells, from a DB query to a SQL server DB. tested on a diferent computer and it worked just fine, so just keep ussing the other computer intead, my first thought was a Windows update problem, i work with diferent computers so was not a big issue. now same problem on all the computers. try to build from scratch, no use. Look like is a ODBC driver problem, cuse in a koworker PC still works, diference is older ODBC driver version, but downgrade ODBC driver version dint fix it for me. anyone with an idea related to this issue?
-
Please provide a minimal, compilable version of your problem. How should we help when you don't post any code.
The latest MSSQL ODBC driver has some problems - I would suggest downgrading it. -
Please provide a minimal, compilable version of your problem. How should we help when you don't post any code.
The latest MSSQL ODBC driver has some problems - I would suggest downgrading it.@Christian-Ehrlicher Sorry din't post any code ralated info, cuse the code has being working just fine for quite a while, most cases having similar problem the working solution was update ODBC driver, but yesterday saw that the tool was working on a diferent computer with older ODBC, so you just have give me the answer. Will test and update the post right after, thanks.
-
ok, i had problems doing the downgrade, sqlsrv32.dll dosnt have a DllUnregisterServer function, so cant just "regsvr32 /u- sqlsrv32.dll".
So my current working solution was just to passed on the connection string.
Like is was:
FileName2 = "DRIVER={SQL SERVER};"
"SERVER=SERVERNAME;"
"DATABASE=DBNAME;"
"UID=USER;"
"PWD=PASSWORD;"
"Trusted_Connection=NO";Working slution:
FileName2 = "DRIVER={ODBC Driver 11 for SQL SERVER};"
"SERVER=SERVERNAME;"
"DATABASE=DBNAME;"
"UID=USER;"
"PWD=PASSWORD;"
"Trusted_Connection=NO";Now all my queries are returning normal values instead of empty ones. Identified drivers giving me this problem, are SQL Server 10.00.19 and 10.00.22. Working ok on ODBC Driver 11 for SQL SERVER 2014.120.55.
