Hello again,
I mentioned before that changing driver version was not likely going to help -
"It's pretty unlikely that code that uses ODBC would simply not work at all with this sort of version problem.
<snip>
I suspect something else is going on. You might have more luck if you provide the error you get in the code, and the version of SQL Server that you're connecting to"
Unfortunately, there definitely is something wrong, as I suspected.
> I believe it should be a matter of just one simple change to my PC
This could be true but what would have made a setting that stops your PC from connecting to an odbc database? This would be an odd thing for a piece of software to do. I can imagine some authentication, encryption and firewall scenarios but error messages would be helpful.
I'd suggest two things -
1) Provide a screenshot of an error message when trying to connect to sql server
2) Use ODBC to connect to something else, e.g. Excel, to see if ODBC is broken entirely
These results would be a good first step, providing clues where to look next. Anyone who guarantees that they can fix things from the details given is mistaken.
As an alternative, you have already spent time and money troubleshooting this. Is another job here on freelancer.com ultimately, going to be cheaper than reinstalling?
Cheers.