ODBC SQL Server Driver Timeout expired (#0) only in Access not in

G

Guest

It seems whenever I run queries against an SQL Server 2005 database I get
an "ODBC SQL Server Driver Timeout expired" error message. However if I go
into SQL view and cut and paste the same command into SQL Server Management
Studio the command runs fine. I don't understand why there would be any
difference????

It is a big database which is properly indexed. Is there something I can
tweak on
the Microsoft Access end so this won't keep timing out????
 
D

Douglas J. Steele

What's your setup? Are these linked tables that you're trying to query, or
is this a pass-through query?

With pass-through queries, you can set the ODBC Timeout in the query
properties. You could increase it from the default 60 seconds, or you can
set it to 0 so that it never times out.
 
G

Guest

These are linked tables and it is not a pass through query. I guess I could
do a pass through query but then why use Access at all? I might as well
stick solely with SSMS....
 
D

Douglas J. Steele

Why use Access? Because it has forms and reports, and because it's very
quick to develop in.

I have to confess I have no idea what SSMS is.
 
G

Guest

Sorry, SSMS is SQL Server Management Studio for SQL Server 2005. It
allows you to run SQL queries. Believe me I am a hardcore programmer
but I prefer the WYSIWYG interface of Access versus cobbling together
ad hoc SQL queries in SSMS.

Basically a pass thru is going to be the same thing as running it in an
SSMS query window, correct??? So that is why I was questioning why to even
bother with a pass thru query as a workaround. At least SSMS will give some
meaningful syntax errors and highlight keywords....

-Peter
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top