D
Doug Steele
I have a split database, with a front end (code, queries etc.) and back end (tables only). Computer A has a copy of both databases, Computers B,C and D have only the front end. Computer A's main menu has an optional timer event which runs every 60 seconds and performs a couple of queries. The queries take less than a second to execute. Whenever the timer event is turned on, it takes the other computers several seconds to open any other screen from the main menu screen (it should take <1 second). When editing, an hourglass appears intermittently and the keyboard locks up for up to 30 seconds. This behavior doesn't occur on computer A. As soon as the timer event on computer A is deactivated, the other computers start behaving normally.
I had a look at the CPU and network usage on computer A and they are minimal.
This is occurring using Office 2003 and Windows XP Pro.
Any suggestions?
I had a look at the CPU and network usage on computer A and they are minimal.
This is occurring using Office 2003 and Windows XP Pro.
Any suggestions?