Timer event causing db slowdown?

[Guest]

I have a split database. Computer A has the front end (code) and the back end (data tables only). Computers B, C, and D have a copy of the front end only. The main menu screen of computer A has an optional timer event which, when activated, runs every 60 seconds and performs a couple of queries. It takes less than a second to execute. Whenever Computer A has the timer event activated, any screen called from the main menu of Computers B,C, or D takes several seconds to load, and when editing fields, an hourglass appears intermittently, the keyboard locks and stays locked or up to 30 seconds or so. This happens even when the tables being edited on computer B are NOT referenced in the timer event code. As soon as the timer event on computer A is deactivated, all the other computers start acting normally.

The computers are running Office 2003 on Windows XP Pro. I have been unable to reproduce this problem on my development machines with Office XP/2000 on Windows XP Pro.

Any suggestions? The CPU usage and network traffic on computer A are virtually nil.

 

[Brendan Reynolds]

A wild guess here, Doug. Try adding a DbEngine.Idle at the end of the code
that executes the queries.

According to the help file, one of the things that DbEngine.Idle does is to
release any locks that are no longer required. My hunch here is that maybe,
just maybe, the apps on the other PCs are waiting for those locks to be
released.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

I have a split database. Computer A has the front end (code) and the back

end (data tables only). Computers B, C, and D have a copy of the front end
only. The main menu screen of computer A has an optional timer event which,
when activated, runs every 60 seconds and performs a couple of queries. It
takes less than a second to execute. Whenever Computer A has the timer
event activated, any screen called from the main menu of Computers B,C, or D
takes several seconds to load, and when editing fields, an hourglass appears
intermittently, the keyboard locks and stays locked or up to 30 seconds or
so. This happens even when the tables being edited on computer B are NOT
referenced in the timer event code. As soon as the timer event on computer A
is deactivated, all the other computers start acting normally.

The computers are running Office 2003 on Windows XP Pro. I have been

unable to reproduce this problem on my development machines with Office
XP/2000 on Windows XP Pro.

Any suggestions? The CPU usage and network traffic on computer A are

virtually nil.