ODBC Timeout error

  • Thread starter Thread starter Microsoft News Groups
  • Start date Start date
M

Microsoft News Groups

I have two databases written in Access2000 with SQL server 2000 backends.

In the last couple of days several forms are coming up with "ODBC error on
linked table: Timeout" errors.

The error occurs when

usingDoCmd.RunCommand accmdSaveRecord

using a SQL statement like
CurrentProject.Connection.Execute "Update tablename Set field = value
Where Index = Ivalue"

and

using a SQL Server stored procedure with parameters @field and @Ivalue
and ADO connection and command objects and calling command.Execute

The error does not always occur.

The error seems to be related to updating rather than creating rows in the
tables.

Any suggestions would be greatly appreciated.

Rod Scoullar
 
I've only had limited experience with SQL Server. But I seem to remember
that in Access, there is an ability to adjust the timeout length on queries.
Since you're getting the timeout error only occasionally, perhaps its just
not being given enough time to complete the operation, based on how busy the
SQL Server database is at the moment with other processes, how big the table
is that's being updated, how many indexes are affected, etc. You may want to
search for an option or parameter that allows you to increase the time out
period by say 50%.
 
John,

Thanks for your interest.

You're right there is a Query.ODBCTimeout property. It defaults to 60
seconds.

I could increase that, but the problem has only just started to occur after
more than 6 months of use. I was wondering whether something else may be
the problem causing the sudden slowdown of response.

The consensus appears to be increased network traffic, so perhaps your
suggestion will be sufficient.

Rod Scoullar
 
Back
Top