>>...;server=192.168.1.202,1433;...
>>
>>For some reason, nothing else worked there (and I wasn't there to watch over the IT guy trying things out), but this did. My 0.02 of your currency of choice.
>
>In case Foxite hadn't come up with the Port-option my first try would have been http-syntax, something like
>
>...;server=192.168.1.202:1433;...
>
>but never had I considered kommata. :-)
>
>At this time, we still use System-DSNs configured via ODBC-Interface. However, after getting more and more trouble due to insufficent customer knowhow and steadily rising hardware and system complexity (CITRIX-TS, load balancing, seerver farms, a.s.o.), we are considering a change form SQLCONNECT to SQLSTRINGCONNECT just to make our supporters work and life a bit easier...

My favourite trick is to build a file DSN as a start, then open it as a text file and just replace all line breaks with semicolons, and that's my initial connect string. The DSNs are connection strings stored somewhere (in the registry, I suppose, for the first two kinds, and the third one is in an obscure folder in an unintuitive location). I'd rather have these strings where I want them, than to rely on Windows to keep them.