Weird solid border on labels for check boxes

[Guest]

Okay, this is weird. We have some check boxes on a form. The border and
background for the labels have been set to transparent. Nevertheless, in some
cases, if you select the check box, a solid border appears around the label.

There are a few instances where this action occurs reliably and others where
it occurs intermittently. Any thoughts anyone?

Thanks.

 

[Van T. Dinh]

IIRC, when you select a CheckBox, the Label attached to the CheckBox will
show a rectangular border.

You can try detaching the Label from the CheckBox.

 

[Guest]

First, thanks very much for your response. I appreciate your taking some time
to consider the problem. Unfortunately, the solution doesn't work. Mostly
because the problem is intermittent. Here are some other things to consider:

First, all our fills and borders are set to transparent, so, while we expect
the faint border around labels for selected items, this is a solid border
that, when it occurs (which is not always) is solid and persistent. But it
doesn't always occur.

Second, among the controls where it does occur, all properties are set the
same. Furthermore, the border doesn't apear around the label for every
selected control, only for some and, as far as we can

Third, and here's the real gem, thank you Microsoft, there's a major bug in
Access 2003 that produces a screen flicker whenever you move your cursor over
an unattached label on a tab page. As a result, we've been busily
re-attaching all those unattached labels we were using for silly, inessential
things like, say, instructions.

 

[Van T. Dinh]

I am using Access 2003 on Win XP, both fully patched and in one of my
databases, I have the 2 things you described:

* CheckBoxes (in my case, in OptionGroup).
* Unaatached Labels on Tab pages.

and I am not observing the behaviours you described. The screen stays
absolutely still in my case.

* Do you have any Timer Event running?
* Are your OS / Access fully patched?

In another thread, using Windows XP Theme seems to be the culprit of some
weird behaviour in Access 2003 which I never experienced using the Windows
Classic Theme. However, I tested all of the above in my database (with or
without Windows Them Control on Forms / Reports option) and I still don't
see the behaviour you described.

 

[Guest]

You wizard! Yep, it's the themes. Thank you so much for taking time to figure
this out. You certainly rate your MVP designation. The themes would never
have occurred to me. We (foolishly) perhaps, use the default theme for the
operating system. When I switched back to Windows Classic, the problem went
away. Of course, so did our lovely new form design.

Ah, well. I make a note in the documentation that the "themes" aspect of
WinXP can have some, well, surprising effects.

Thanks again, very much.

r

 

[Van T. Dinh]

You're welcome ...

I wasn't aware of this until recently as I actually preferred the Windows
Classic interface.

If you wants to use Windows XP Theme, reset your OS back to Windows XP Theme
but in Access, use the Menu Tools / Options / Forms_Reports and uncheck the
option "Use Windows Themed Controls on Forms". I am not 100% sure but I
tested my database on Windows XP Theme with the option unchecked and it
still behaves normally.

 

[Guest]

Yep, it works, but the price is too high. We really like the lighter XP
design style, especially because most of our users and non-tech types who are
often intimidated by software. Besides, they're hospital staff, so they need
all the cheering up they can get.

Thanks again.

r

 

[Guest]

A final word on the color issue. Turns out you can control whether or not the
control color changes with changes in Windows themes. To permanently set the
color, use a postive number. Negative numbers indicate colors that change
with Windows themes. Just a tidbit from browsing through Wrox's "Acess 2003
VBA."

r

 

[Guest]

Okay, this is getting truly strange. We have have one form (out of 23) which
is not opening on the machines of two of our clients. All the other forms
open. To make things worse, we can't reproduce the problem on our machines,
which makes it difficult to track down. So I guess the question is: what
factors do you know of that might prevent a form opening.

I have tried changing the Access macro security settings, but they have no
effect. What's so odd is that it's just this one form. We have tried it in
all versions of the application file, and it works fine every time. And
what's really weird is that it's a very small, very simple form. Basically
it's just three buttons and a text box.

Settings are: modal = yes, popup = yes, border = dialog, auto resize = yes,
auto center = yes.

Any ideas?

Thanks very much.

r

 

[Van T. Dinh]

Generally, when the same version of a Front-End works on most machines
except a few, the likely problem is missing References or errors in the
References collection on the Front-End.

You need to check the References on the problematic PCs.

See if the following The Access Web article helps:

http://www.mvps.org/access/modules/mdl0022.htm

 

[Guest]

You really are a wizard. You're exactly right; it's the references. So here's
our big question:

We're creating the installation package including the run-time application
and a dll from a third party (DynaZip). We’re using the Access 2003 packaging
wizard. Is it sufficient to merely include a copy of the dll placed in the
same folder as the installed application, or is it necessary to register the
dll? If it’s necessary to register it, can we do that using the packaging
wizard?

And by the way, is there any way we can tell Microsoft just how much of a
wizard you are?

r

 

[Van T. Dinh]

Afraid the P & D (Packaging & Deployment) in not my strong point since I
never had to do it. However, if my understanding is correct, the P & D will
automatically include a copy of the DLL in the installation package, copy
and register it onto the target PC.

There should be a number of documents that come with your VSTO + Access
Developer Extensions software package the you got.

If you have any problem with the ADE, post your queston to the newsgroup
"microsoft.public.access.devtoolkits".

Thanks for the compliments but I don't know how you can tell Microsoft
(another one of my weak points). I do know though, there are other people
who know more about Access than I do.

 

[Van T. Dinh]

I haven't read this but see if it helps:

http://msdn.microsoft.com/library/d.../en-us/odc_ac2003_ta/html/odc_acdeployADE.asp

--
HTH
Van T. Dinh
MVP (Access)



news:[email protected]...

 

[Guest]

Thanks very much for taking time on this problem.

r