I do not have the same problem with Access 2003 and Windows XP Pro.

Note: I do not have problems with a SQL 2005 server that is on the local
network. Only accessing a hosted SQL server. Is this perhaps a ODBC time out
problem?

We have several Access XP databases that link to a SQL 2005 database. Most
every user does not experience this problem with the exception of one user.
Whenever this user attempts to open a table or run a query she receives the
error. If she drops and then reattaches the table, she is fine for a while,
but the problem inevitably returns. She did not have this problem before
changing the server to MS SQL 2005 (We dropped and reattached all tables
after the upgrade).

She is a developer and has the SQL Server Management Studio on her machine,
as well as a SQL 2005 server. With either of these has come the native SQL
2005 client. We have tried both ODBC clients and neither fixes the problem.

We are currently seeking a solution as it impacts development. Last week I
setup a new computer for her, but the problem has surfaced on the new laptop
as well, leading me to believe that it was installed with a software package
or service pack.

Geoff

The SQL 2005 database I inherited from my bro-in law has tables with names in
the spaces and spaces and other characters in the column names. I link to
these tables in an MDB file. Access 2003 sees this fine, but Access 2007
returns odbc--call failed errors when attempting to access the tables. Is
there anything I can do short of removing the spaces and characters (? %)
from all of the table and column names? Is there a switch I can throw that
will tell Access 2007 to ignore this and work like a previous version?

Thanks