Bad Focus in database window

[Guest]

I have Access XP SP3 and Access 2003 SP2 installed on my machine which is
running Windows XP Pro, SP2. At some point in at least the last 6 months, I
have had problems when selecting objects in a query window. When the problem
first started, I only had Access XP SP3 installed. Because of some other
error I was getting, I added Access 2003 SP2 a couple of weeks ago. (I have
both installed due to differing programming needs.) I hoped that 2003 would
fix my problem but it persists. Two other people in my office have tried
opening a copy of my database on their machines and have NOT had the problem.
Both of them are running Windows 2000. One of them has Access XP and the
other has Access 2003.

Steps to recreate:
Open an existing query. (Note: The focus is set to the field name of the
first column.)
Click on the top of the table in the design window to move it. I find that
I cannot move the table UNTIL I either click on a field listed inside the
window OR click on the title bar for the query.

I find a similar problem when I have more fields than the window can
display. When I click on the scroll bar across the bottom, it only responds
a short distance before it stops. Once I have clicked on the title bar for
the query, the scroll bar works as expected when clicked.

I am wondering if anyone else has encountered this and if so, have they
discovered how to fix it.

Thanks,
JoAnn

 

[Guest]

Just a WAG but go to Tools, Options, General Tab and turn off Name
Autocorrect. IMHO it's a piece of do-do and the cause of many problems. While
there turn off Compact on Close if enabled. You'll be glad that you did.

Next WAG is to temporarlily turn off your virus checker and see if that
helps. If so you can usually exclude the scanning of .MD* files.

 

[Guest]

Thanks for your response, Jerry.

I do not have Name AutoCorrect turned on. I use Compact on Close very
sparingly, as well, so it is not on in this database. I did try turning off
my virus protection, then reopened the database and still the same results.
Interestingly, I found that when I took focus away from Access to turn the
virus protection back on, the query window worked as I would expect when I
returned focus to Access. I tried this several times by clicking a different
icon in my taskbar, then clicking back to the Access database. I am
wondering now if this might be an issue with the operating system? Any ideas?

JoAnn

 

[Dirk Goldgar]

In

I have Access XP SP3 and Access 2003 SP2 installed on my machine
which is running Windows XP Pro, SP2. At some point in at least the
last 6 months, I have had problems when selecting objects in a query
window. When the problem first started, I only had Access XP SP3
installed. Because of some other error I was getting, I added Access
2003 SP2 a couple of weeks ago. (I have both installed due to
differing programming needs.) I hoped that 2003 would fix my problem
but it persists. Two other people in my office have tried opening a
copy of my database on their machines and have NOT had the problem.
Both of them are running Windows 2000. One of them has Access XP and
the other has Access 2003.

Steps to recreate:
Open an existing query. (Note: The focus is set to the field name of
the first column.)
Click on the top of the table in the design window to move it. I
find that I cannot move the table UNTIL I either click on a field
listed inside the window OR click on the title bar for the query.

I find a similar problem when I have more fields than the window can
display. When I click on the scroll bar across the bottom, it only
responds a short distance before it stops. Once I have clicked on
the title bar for the query, the scroll bar works as expected when
clicked.

I am wondering if anyone else has encountered this and if so, have
they discovered how to fix it.

Thanks,
JoAnn

I have recently been experiencing what seems like the same problem,
using Access 2002 and Windows XP SP2. I haven't investigated it because
I've been swamped and can work around the problem, but I strongly
suspect that it's a bug in Windows XP -- possibly a display driver
issue, but something that came with a relatively recent system patch.

 

[Guest]

Thanks for your response, Dirk. Since no one around me is getting the same
problem, it is nice to have someone else validate that they are getting it as
well. Now to find out how to fix the problem.

JoAnn