Access report with SQL server BE hangs on one p/c but not others

Hi
I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
back end (using ODBC).
Can anybody explain to me why one p/c should have a problem with one
report? When you click on the button which runs the report, the egg
timer comes on for about 10 minutes and then the following error is
displayed:
Connection failed
SQL State '01000'
SQL Server error 53
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied
All other reports in the Access application run fine on this p/c. The
report itself runs fine on all other p/cs that I have tried it on. The
same error occurs whichever user is logged onto the p/c.
Can anybody make any suggestions as to what might be going on?
Thanks
Colin
Booby
At first glance it seems that this specific report is connected to SQL
Server with 'wrong' login or to 'wrong' database. Also it could permission
issues
Can you compare everything with 'working' reports?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1180954455.134604.78650@.w5g2000hsg.googlegrou ps.com...
> Hi
> I have a MS Access database which uses SQL server 2000 (SBS 2003) as a
> back end (using ODBC).
> Can anybody explain to me why one p/c should have a problem with one
> report? When you click on the button which runs the report, the egg
> timer comes on for about 10 minutes and then the following error is
> displayed:
> Connection failed
> SQL State '01000'
> SQL Server error 53
> [microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
> Connection failed
> SQL State '08001
> SQL Error 17
> [microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
> or access denied
> All other reports in the Access application run fine on this p/c. The
> report itself runs fine on all other p/cs that I have tried it on. The
> same error occurs whichever user is logged onto the p/c.
> Can anybody make any suggestions as to what might be going on?
> Thanks
> Colin
>