Command Button problem (resolved-but weird)

I've got a command button on my form, actually, the same thing is happening on two forms.

Once this button is pressed, it does what it's supposed to and works fine. But, if a form is opened and displayed over this button, then that form is closed, the command button graphics show the graphics from the form that opened over it. I've tried refreshing the form and the button and neither worked. The button still works like it should, just has the graphics from the other form "burned" on top of it. It's set to graphical style and has a colored background. The button is also situated on a label on the form, same type of button that's not on a label doesn't have this problem.

The "burn" affect doesn't happen untill after the button has been clicked at least once. Then if a form opens on top of it, that forms graphics burn onto the button.

Any ideas?

This is what it looks like - the bottom right corner with the piece of the information bubble thing is supposed to be a light blue button that says new search. This is what it looks like after a message box displays on top of it.

Forgot the attachment:

try setting the form to AutoRedraw = True?

Good thought, didn't work though. Still doing the same thing.

Hi,

Bring the button to top most level.

In design time. right click the button and click on Bring to Top.

This type of problem happens when we have a control and a lable on it.. and if the lable is transperent seems right in design mode but not during runtime.

Regards,
Pradeep

Thanks for the input, unfortunately it didn't work. The button was already brought to front, double checked that, still the same behavior. So, I tried to send the label it sits on to back and the button to front, but I'm still getting the same behavior.

Any other ideas, anybody?

Hi,

Send me the code I wil try fix it..

Thanks for the offer. Looks like I've got it fixed though. How freakin annoying and odd. What I did in the buttons click event was set "usemaskcolor = false" and it fixed it. Funny thing is, the usemaskcolor property has always been false and still shows as false in the properties window. I never mess with that.

The button unloads the form, then loads it again and changes a few booleans, that's about it. I just tacked on the usemaskproperty = false after all that.

I'd be interested to know why this happened and why I'd have to set it to false if it already is false.

Thanks for the replies and offers to help.

well, i can think of a normal ocx, these have "set property"
which runs some code,
aparently there is bug somewhere (maybe in the ocx itself,
maybe your code), but when the set property code runs
it fixes something....