469,086 Members | 1,146 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,086 developers. It's quick & easy.

A2003 Text Boxes Cause Screen to Flutter

Text boxes that are not grouped with a data control seem to cause my
screen to flutter when the mouse passes over it. Does anyone know why
this might be?
--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Nov 13 '05 #1
7 1620
Eh? Data Controls are a VB artifact, not an Access Control. Can you clarify?
Is your application a VB app or an Access app? If an Access app, do you mean
"unbound controls"?

Larry Linson
Microsoft Access MVP
"Tim Marshall" <TI****@antarctic.flowerpots> wrote in message
news:ci**********@coranto.ucs.mun.ca...
Text boxes that are not grouped with a data control seem to cause my
screen to flutter when the mouse passes over it. Does anyone know why
this might be?
--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

Nov 13 '05 #2
This happens to me over a list box in Access 2000. I just avoid hovering
the mouse over it.

dixie

"Tim Marshall" <TI****@antarctic.flowerpots> wrote in message
news:ci**********@coranto.ucs.mun.ca...
Text boxes that are not grouped with a data control seem to cause my
screen to flutter when the mouse passes over it. Does anyone know why
this might be?
--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

Nov 13 '05 #3

"Tim Marshall" <TI****@antarctic.flowerpots> wrote in message
news:ci**********@coranto.ucs.mun.ca...
Text boxes that are not grouped with a data control seem to cause my
screen to flutter when the mouse passes over it. Does anyone know why
this might be?
--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto


Widely known problem with Access 2003 forms related to "inheriting" desktop
theme, which you must set to "Classic" to stop the fluttering. Microsoft is
in denial about the problem. (Access 2003 has many more bugs related to its
interaction with the system GDI, which you will probably soon discover.)
Nov 13 '05 #4
This flaw is triggered by an intaction by themed controls in Access 2003 and
Windows XP.

If a label is unattached and has a parent other than the form itself (e.g. a
tab control or option group), and Windows XP themes are enabled, then the
flicker occurs.

For more details, and code to work around all affected controls in your
database, see:
http://members.iinet.net.au/~allenbrowne/ser-46.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tim Marshall" <TI****@antarctic.flowerpots> wrote in message
news:ci**********@coranto.ucs.mun.ca...
Text boxes that are not grouped with a data control seem to cause my
screen to flutter when the mouse passes over it. Does anyone know why
this might be?
--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

Nov 13 '05 #5
Larry Linson wrote:
Eh? Data Controls are a VB artifact, not an Access Control. Can you clarify?
Is your application a VB app or an Access app? If an Access app, do you mean
"unbound controls"?


Larry, I should have said text boxes.

It is happening in an app I successfully converted from A97. There is a
tab control containing several label controls on different tab pages
that are standing alone, ie, are not associated with a text box or other
control.

When I pass the mouse over the unassociated label, the whole tab control
begins to flutter - it blinks when I first go over the unassociated
label and then again when I leave the unassociated label.

It does not occur when I pass the mouse over label controls that are
grouped with a text box or even a subform.

It also does not occur if I have an unassociated label outside of a tab
control.

There are no events for any of the offending labels.

It's interesting - when I create a label and error checking is turned
on, A2003 tells me I have an error when I create an unassociated label.
Is it best design practice to use a text box with a string value
(perhaps enabled = 0 and locked = -1) instead of label that is not
associated with anything?

--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Nov 13 '05 #6
"Tim Marshall" <TI****@antarctic.flowerpots> wrote
It's interesting - when I create a label
and error checking is turned on, A2003
tells me I have an error when I create
an unassociated label.
Yes, I guess I must have turned that off because it was an irritant to me,
as well.
Is it best design practice to use a text
box with a string value (perhaps enabled = 0
and locked = -1) instead of label that is not
associated with anything?


I don't do that, unless there are going to be frequent changes to the
information displayed in Labels (a rare occurrence, in my experience).

Larry Linson
Microsoft Access MVP

Nov 13 '05 #7
Thanks to Larry, dixie, no nan and Allen Browne replied, despite my
confusing the issue by using wrong terminology! 8) I've been absent
from the group for a long time and it's very reassuring both seeing the
"old faces" I'm familiar with and also newer (to me) folks who are able
to help me out.

I appreciate your taking the time.

--
Tim - http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Nov 13 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

12 posts views Thread by dixie | last post: by
9 posts views Thread by B-Dog | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by kglaser89 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.