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