>I've had it happen but using ADO. The fun there is that the provider returns "Exception code 0", which gives no clue. Upon trying numerous things, I finally looked up the MDAC version and sure enough the PC that was failing to connect had a different version.
>
>If you do need to fix the driver versions, the MDAC component checker will come in handy, download it from http://www.microsoft.com/data/download.htm.

Thank you very much. I will look at this and see if the MDAC version at the "problem" client is different than the working clients.

Mat