D
Dave Rodenbaugh
Hi,
Having a problem with MS Access 2003 on a Pentium 4 with Office 2003,
Windows XP Pro.
My file is Access 2000 format, and the recent upgrade to Office 2003
seems to have introduced a small update lockup. After some period of
time during a form open/close or a dialog switch, the UI will appear
unresponsive. Unlike a process lockup, where the Task Manager will
indicate the process is not responding, this one seems to be temporary
because opening the Task Manager and simply cancelling out of it
'unlocks' the UI again for a short while longer. The process is
always responding according to the Task Manager.
When it does lock up and I already have Task Manager up, I can see
that the processor shows about 41% and there is some nominal network
activity. Other than that, I can't seem to find out where this thing
locks up.
Other info: This application worked FINE under WinXP Pro/Office XP
and Win 2K/Office 2000. Also,quite strangely enough, with Office 2003
and Win XP using a Pentium 3, I can't reproduce the problem, so I'm
suspecting the P4 chip. (This suspicion is deepened by the fact that
when I turn off the hyper threading (simulated Dual CPU on a single
processor feature, new for P4), the frequency of this problem lessens,
but does not go away.
Other things I've tried with no success:
- Upgraded the project to Access 2003 format
- Removed Form.Repaint calls
- Removed Filter properties
Any help would be appreciated.
Thanks,
-Dave Rodenbaugh
(e-mail address removed)
Having a problem with MS Access 2003 on a Pentium 4 with Office 2003,
Windows XP Pro.
My file is Access 2000 format, and the recent upgrade to Office 2003
seems to have introduced a small update lockup. After some period of
time during a form open/close or a dialog switch, the UI will appear
unresponsive. Unlike a process lockup, where the Task Manager will
indicate the process is not responding, this one seems to be temporary
because opening the Task Manager and simply cancelling out of it
'unlocks' the UI again for a short while longer. The process is
always responding according to the Task Manager.
When it does lock up and I already have Task Manager up, I can see
that the processor shows about 41% and there is some nominal network
activity. Other than that, I can't seem to find out where this thing
locks up.
Other info: This application worked FINE under WinXP Pro/Office XP
and Win 2K/Office 2000. Also,quite strangely enough, with Office 2003
and Win XP using a Pentium 3, I can't reproduce the problem, so I'm
suspecting the P4 chip. (This suspicion is deepened by the fact that
when I turn off the hyper threading (simulated Dual CPU on a single
processor feature, new for P4), the frequency of this problem lessens,
but does not go away.
Other things I've tried with no success:
- Upgraded the project to Access 2003 format
- Removed Form.Repaint calls
- Removed Filter properties
Any help would be appreciated.
Thanks,
-Dave Rodenbaugh
(e-mail address removed)