>Scott,
>
>Looks like the driver you had is in MDAC 2.5 SP 1.
>
>See http://www.microsoft.com/data/MDAC25info/MDAC25SP1Manifest.htm
>
>Perhaps someone else can help you with the problem of how to get the old drivers and the new ones on the machine at the same time.

Hi Cindy.

Thank you for your response.

It's 10:15pm on the west coast here and I just found a way to correct the situation.

The network admin at this client site has been using the ip address of the sql server as the server name in the DSN. From my understanding ... a perfectly legal practice..although I'm not sure why this is being used here.

I found some similar bug articles on the MS knowledgebase re MS sql6.5 specifically, and the client trying to load an older version ... anyways .. that wasn't the issue. But it got me trying a different tactic.

I eventually changed the servername of the DSN to the hostname ... and poof! it works.

Go figure... with the latest version of the mdac on the client, using the ip address as the name will not work on with TCPIP as the client's networking lib ... but using the ip address as the name still does work for named pipes and multiprotocol...

So, without having to change their production server .. it now works with TCPIP as well.

Weird.

I'll be telling them to use a hostname from now on ...makes more sense ...

Scott