John Skolits
askolits at ot.com
Tue Oct 3 11:13:04 CDT 2006
I have a bunch of reports that run at night (within Access MDB). The database is triggered by using command line arguments. Sometimes, I get an ODBC timeout error, but it's very inconsistent. I set all the query ODBC timeouts to 300 seconds. These routines run at about 2:30 AM to avoid heavy server loads. But, I do know, there are other backups and such running that take processor time, but my MDB queries typically run very fast. Is it possible SQLServer is timing out instead of Access and that's why the messages are happening. There are many more ways I can optimize the queries, which is the next step, but how to I find out what the SqlServer ODBC timeout value is and how do I change it? John