>Randy,
>

>That's odd...what version of the Framework are you using?

6.1.2


>What version of Visual FoxPro?

VFP 7.0 SP1


>If you're using VFP7, you can use the MouseEnter and MouseLeave events of each control instead...

What would I do with these?

>also, you may want to look at VFP7's hot tracking...if it does what you want, you may not even need to use the FX controls.

Hot tracking would work if I could get the buttons to look like buttons. With hot tracking enabled, and setting the visualeffect property of each button to 1 in the form.init(), the hot tracking disappears. I assume that hot tracking uses the visualeffect property to show the effect on the buttons. I know this is MS new look, but for several buttons on a form, it's kinda confusing. MY BOSS WANTS BUTTONS! :)


We have one possible solution that I need to ask you about. We dropped the foxpro base commandbutton in a container, and drew the 3D lines around it and called it acommandbutton. Then drop that on a form and set hot tracking on and it works and looks like we like it. It also allows the form to release from memory correctly. How is this going to effect framework controls if we base ccommandbutton on our acommandbutton? Are we going to break everything? If we don't do it at the ccommandbutton level, we'll have to change it at the form level, which will be mucho worko. We subclassed some buttons, but used framework controls in many places.


HELP!!!!!:)