> This error only occurs on the production computer - the queries work fine
> in
> the test environment.

I am no professional in Sql-Server, however, I had no problems when testing,
too. Using the productive linked servers in my case caused many, many errors
when running queries against it so I had to give up using the linked servers
directly. Instead, I use a stored procedure in SQL-Server that makes copies
of the tables from the linked server regularly (like: INSERT INTO
CopyOfTABLE SELECT * FROM LINKEDSERVER...TABLE, or with the openquery-syntax
if it does not work otherwise). Then I query the copies instead of the
linked originals. This may cause other problems, it works for me.

My linked database is a Firebird DB.

There are various errors comming from drivers or from the database that I
could not even solve with commercial driver software for firebird or the
vendor or my Firebird DB or developers from firebird. I spent many hours to
find out that sometimes different DB's do not work together (MS or anyone
else would never tell you immediately). I did not have any problems running
queries from Access to the database directly, no problems to run queries on
copies of the tables in SQL-Server (testing) - but almost nothing worked
when using the linked tables (productive).

Using linked servers, sometimes you have to convert columns, sometimes you
need the openquery-syntax (if you do not need to many apostrophes...) or
sometimes the queries just fail (because some fields "appeared" during
runtime, etc. etc.).

It's just a pain, so be prepared to face trouble.

arno