Access XP and flaky behavior

M

Mark

I've noticed some flaky behavior using XP, and I was
wondering if anyone else has the same problem.

First, when I'm in the database and I'm switching between
the tables and queries, it takes a long time to update
the list of query names or table names. This can take
several seconds and occasionally the application will
just hang while rebuilding the window until I leave the
Access session and return to it.

I also run a lot of visual basic routines, and frequently
I open a second session of Access while they are running,
sometimes even opening the same database. What happens
frequently is that while I'm working in the second
session, the first session pops up on the screen. Since
the VB is just running queries I wouldn't expect it to
open the Window again.

Does anyone have any ideas of why these things could be
happening? I'm also using Windows XP for the operating
system. Thanks

Mark
 
A

Allen Browne

Regarding the slow updates, make sure you uncheck the Name AutoCorrect boxes
under:
Tools | Options | General
This mis-feature causes so many problems. More than a dozen are listed here:
http://allenbrowne.com/bug-03.html

Up to Access 97, VBA was built into Access, and the windows behaved
correctly. In Access 2000, Microsoft removed the integrated code editor and
shacked Access to a separate version of the VB editor. To say there is not a
happy marriage between the two independent windows is an understatement. The
windows don't pop up correctly, and their own popups can appear incorrectly,
or even over other processes. They appear to have patched up some of the
issues in later versions, but the underlying problem is manifestly still
there.

It gets worse when you try to run two instances of Access, or two versions
of Access at the same time. Due to the loose coupling of the Access and code
windows, Access can even get confused about which code window belongs to
which instance. On one occasion, I had a copy of A2002 open, with its code
window, which I opened a copy of A2000 and created a new mdb. The new mdb
was assigned the wrong Office library (presumably because of the other
version open at the same time), and so ended up being completely unusable,
and that project had to be restarted.

These problems have been around for 4 years now, through 3 different
versions, and numerous service patches, so we have no choice but to learn to
live with the flaky behavior if we are to keep using Access.
 
Top