S
Smidge Boyter
I have a form that uses the default record navigation by Access. When a
user makes a change to the form and moves off the record, Access goes to
update a linked SQL Server table. I get a timeout error:
ODBC - Update on a linked tabled 'dbo_tblProductMaster' faled.
[Microsoft][ODBC SQL Server Driver] Timout expired (#0)
I used SQL Server's profiler and captured the update statement and ran it
directly on SQL Server. It times out in Query Analyzer as well. The table
has about 45 columns and the where statement on the update is passing in
every single column value in the where clause, I imagine to handle
concurrency issues.
Is there anything I can do to change the Where filter so it uses only 2
columns, primary key and a last updated date column (this is how we handle
concurrency for our other applications)? Can I override the query that
access creates and write my own by overriding an event handler?
Thanks for any advice you can give...
user makes a change to the form and moves off the record, Access goes to
update a linked SQL Server table. I get a timeout error:
ODBC - Update on a linked tabled 'dbo_tblProductMaster' faled.
[Microsoft][ODBC SQL Server Driver] Timout expired (#0)
I used SQL Server's profiler and captured the update statement and ran it
directly on SQL Server. It times out in Query Analyzer as well. The table
has about 45 columns and the where statement on the update is passing in
every single column value in the where clause, I imagine to handle
concurrency issues.
Is there anything I can do to change the Where filter so it uses only 2
columns, primary key and a last updated date column (this is how we handle
concurrency for our other applications)? Can I override the query that
access creates and write my own by overriding an event handler?
Thanks for any advice you can give...