No it wouldn't. It doesn't take into account driver might not be installed at all. In setup step2 it lets you choose ODBC drivers to deliver (however as expected suggests separately delivering MDACTYPE.exe)
I don't know how you would get NT pw. But say for example SQL server supports a 'Trusted_connection=Yes' parameter instead of 'User ID=...;Password=...'. Might there be something similar.
Using control panel create a file dsn. Open generated .dsn file in notepad and you could get the parameters from there.
Cetin

>Cetin,
>
>That was fast and I'm very grateful.
>
>Let's say the backend is DB2 and there is nothing on the PC that smells even remotely like DB2.
>
>Will your suggestion still work, or will I need to install DB2 ODBC drivers on all machines?
>
>And another question: How do I get the NT/Windows user id & password and use it in the connection string?
>
>
>>>The product is finallly ready, it's tested and bug-free :-\, (sorry I just couldn't help myself) and all that's left to do is go to the client's site and install it.
>>>
>>>Oh and btw, while you're at it, you also need to go to a couple of thousand user's PC's and manually set up ODBC and the DSN's.
>>>
>>>I'm pretty sure, or at least I hope, that this is not how it's done.
>>>
>>>But how is it done?
>>
>>Peter,
>>I think there is a file for this in downloads area.
>>What I do is a little different and I prefer no to setup ODBC at users registry. Instead I use SQLStringConnect() or 'Create connection ...'
>>A connection string looks like :
>>'DRIVER=SQL Server;SERVER='+lcServerName+';User Id='+lcUserId+';Password='+lcPw
>>Cetin