I enherited an access db that is shared by multiple users (all are hitting the same file on the network) with linked tables to a Sql 7 back end. Everything was working fine until our company started replacing old machines. So on the new machines I would set up the DNS and it will test fine. The problem is that when I refresh the links on one machine I get this ODBC --call failed message on the other machines. I thought it was different versions of MDAC but after some testing, I'm ruling that out. Any ideas would be appreciated.

Thanks!!!

I have had something simular happen to me in the past.

Try searching the registry for ODBC and find a time out there somewhere. This was set to low in my case and caused time outs which in turn returned the Failed error....

Try it...

Regards

I can get it to work on any one machine so I don't think it is a timeout issue. It only works on the machine where I refresh the links.

?????

Refreshing links is much more timeconsuming than using the link "normaly" but if you are sure that is not it then its not it. Just thought i would post that i have had something simular and after searching for a day it turned out to be just that. (They had just gotten new machines as wel. After install the timeout was set to 60 (default) and needed at least 120 (old was 240) seconds that is....)

Sorry for my "bad" suggestion.....

Regards

Hey check the ODBC connection properties. The Data source name has to be the same as the first computer which was first set up. Let me know.

all the ODBC data source names are identical on all machines it should work. So if half have one name and other half have another name then only the half will work at a time depending on which machine I refresh the links from??