By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,384 Members | 845 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,384 IT Pros & Developers. It's quick & easy.

ODBC Errors

P: n/a
We connect via terminal services to an excel spreadsheet that has an
ODBC link to an access database using a pivot table, when we try to
refresh the data within the excel spreadsheet we receive the following
error "the microsoft jet database engine cannot find the input table or
query....."

this works ok if the user connects to terminal services as the
administrator however if they connect as any other issue it won't work

Anyone got any ideas?

(have tried 2000 ts and 2003 ts)

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
pa*********@hotmail.com wrote:
We connect via terminal services to an excel spreadsheet that has an
ODBC link to an access database using a pivot table, when we try to
refresh the data within the excel spreadsheet we receive the following
error "the microsoft jet database engine cannot find the input table or
query....."

this works ok if the user connects to terminal services as the
administrator however if they connect as any other issue it won't work

Anyone got any ideas?

(have tried 2000 ts and 2003 ts)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Since the original connection is thru TS, the login name may not have
permissions to the folder where the Access DB lies.

Usually a link between Access & Excel doesn't require an ODBC
connection. Any connection string that allows access to an Access (JET)
DB will have UID (user name)and PWD (password) parameters (if required).
You can set the UID to Admin and the PWD to whatever the password is:

...;UID=Admin;PWD=OpenSesame;

I'm not sure if this will solve your problem, but worth a try. I
believe the answere lies in the TS permissions for the login in.

BTW, a TRUE ODBC connection string will look something like this (a DSN
less connection string to SQL Server):

ODBC;Driver={SQL Server};Server=MyServer;Database=MyDB;UID=sa;PWD=a bcd

An ODBC connection string always has ODBC at the beginning.

A connection to an Access table, using JET:

DATABASE=C:\My Documents\Utilities.mdb;UID=Admin;PWD=abcd
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQnkh/YechKqOuFEgEQLf1ACgt+xPE3I78FyhUj00RHpyP3JuB7UAoKy C
UzSMz87/3p0FV5zPUDRDw2Nq
=5YsJ
-----END PGP SIGNATURE-----
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.