In our product, instead of using standard command buttons, I have created a class with a container that acts as such(this way I can put numerous items on the button, change the color of it, etc.). The mousedown event changes the top/left coordinates, changes the specialeffect, pauses a fraction of a second(using inkey(.00001)), and then changes the container button back to normal-- to simulate it being pressed down, and popping back up.

One major problem that this introduces, is timing issues. Foxpro doesn't give priority to the mousedown() event on the container over everything else(as it does with standard command buttons and keyboard interaction). Therefore, the buttons can appear very sluggish. This is very evident when there is a timer object on the form(even with an interval of 2200(2.2 seconds)). I disable the timer as soon as the mousedown event fires, but it is still too sluggish. This is on Celeron 333 class machines. Any tips would be greatly appreciated-- I know I can probably get a 3rd party ActiveX control, long-term, but right now I need a quick fix if possible-- please reply with any possible fix. Thanks a ton!