Assuming both are installed, that is good. It always seemed a little bizarre to me that out of 100 workstations running Win 7, maybe 30 could run either one, 35 only odbc and 35 only native.


>>Nothing to do with which one is installed. Some machines only one of them will work.
>
>The trick may still work - give them to try each until they hit one that works, then use that for that workstation. Perhaps set the timeout to something shorter than the default minute while trying out.
>
>>>>Excellent for finding the latest driver, kudos. But my experience has been that on many machines only one of the drivers, odbc or native, will work at all. IOW on machine A only odbc works, on machine B only native works, on machine C either one works etc. Never been able to quite figure out the how and why.
>>>
>>>It depends on which one is installed on each. Now with my luck you can't rely on any particular one being everywhere except the oldest, for SQL 2000, because you don't have access to all workstations and you can't trust their IT guys to install anything.
>>>
>>>My trick is to have several connectstrings, not as automated as what Tore posted, but these connectstrings mostly differ in the driver (or, in one case, in the address of the server, because they have two NICs on it and some workstations see it by name and the others by IP adress number), so they each use what works for them (first time try each, save the ordinal number of one that works, go for that one henceforth).