buddles
asked on
colour combo box screen refresh
Hi Guys, I wonder if anybody else has come across this problem?
I have developed an Access database in 2003 and migrated it to 2007. I have a main input form and another smaller form as a pop up. the combo boxes on the main form have a white background but when the pop up form is moved over them the combo boxes get repainted with the main forms background colour. we want all combo's text and other boxes all to remain white. we have found that this occurs with access 2007 with windows XP and windows 7
Any ideas as always will be much appreciated.
I have developed an Access database in 2003 and migrated it to 2007. I have a main input form and another smaller form as a pop up. the combo boxes on the main form have a white background but when the pop up form is moved over them the combo boxes get repainted with the main forms background colour. we want all combo's text and other boxes all to remain white. we have found that this occurs with access 2007 with windows XP and windows 7
Any ideas as always will be much appreciated.
have you installed the Office 2007 SP2?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
well done and thanks for your quick and accurate response
Glad that helped out - that issue makes for a very annoying user interface.
Just a note...The purpose of the Alternate Background property is to display alternating colors in a continuous form or datasheet view of the form. It is just by some bug that it also affects your controls' backgrounds in single form view (where it should have no effect at all). As far as I know, this issue is not present in Access 2010.
Just a note...The purpose of the Alternate Background property is to display alternating colors in a continuous form or datasheet view of the form. It is just by some bug that it also affects your controls' backgrounds in single form view (where it should have no effect at all). As far as I know, this issue is not present in Access 2010.