ODBC TIMEOUT INSERT/UPDATE

[BillyBob]

I don't know if this is the right forum but what the
heck..

My office has been using a MS Access 2000.mdb as a front
end to a SQL Server 2000 database.

(read my whole post if your wondering why I chose this
forum)

It's been working fine now for 1 1/2 yrs.

Latley, in this one particular form, when a user tries to
insert a new record, it sometimes sits for a long time
and then timesout. The insert or update only involves one
table
(which has about 6,000 + records although, the forms
recordsource pulls just over 1000).

Unfortunalty, the problem has been getting gradually
worse and the timeouts are happening more and more
frequently. In fact, the whole front feels to me like
every query is slowing down (but very rarly times out
overall).

To help the users, I created a .mdp file that has a
single form that allows them to insert/update to this
particular table. It's very limited but at least for now
they can work (but they still have to use the main app).

To import all the objects from the .mdb into a new .mdp
would take way too long in fixing all the code issues and
other errors that will surley crop up.

I've tried:
1. dropping all of the linked tables and re-linked them.
2. http://support.microsoft.com/default.aspx?scid=kb;en-
us;305617
3. limited the number of records in the recordsource to 1
at a time
4. shut down other SQL databases that aren't being used
5. Removed subforms that have related tables (although,
these weren't being updated)

If anyone has any ideas or suggestions I would really
appreciate it.

Thanks!

 

[Pavel Romashkin]

Have you tried to limit the number of records the form's record source
is using? I can't imagine the user needing all 1000 records at the same
time, especially if what the form is doing is *inserting*. 6000 records
is nothing to the server, so the problem must lie in the FE or the network.

Pavel