Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / September 2006

Tip: Looking for answers? Try searching our database.

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

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Peter S. - 06 Sep 2006 13:05 GMT
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????
Douglas J. Steele - 06 Sep 2006 13:26 GMT
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.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> 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
[quoted text clipped - 6 lines]
> tweak on
> the Microsoft Access end so this won't keep timing out????
Peter S. - 06 Sep 2006 13:40 GMT
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....

> What's your setup? Are these linked tables that you're trying to query, or
> is this a pass-through query?
[quoted text clipped - 13 lines]
> > tweak on
> > the Microsoft Access end so this won't keep timing out????
Douglas J. Steele - 06 Sep 2006 16:14 GMT
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.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> These are linked tables and it is not a pass through query. I guess I
> could
[quoted text clipped - 22 lines]
>> > tweak on
>> > the Microsoft Access end so this won't keep timing out????
Peter S. - 06 Sep 2006 19:14 GMT
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

> Why use Access? Because it has forms and reports, and because it's very
> quick to develop in.
[quoted text clipped - 27 lines]
> >> > tweak on
> >> > the Microsoft Access end so this won't keep timing out????
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.