Chris,

Why not move it off form entirely? ie .Top = -100, .Left = -100

>Basically, we have a form that performs an action that really hogs the CPU. Its a thermonitor to indicate the progress of an task. We used to have an "Cancel" button on the form. If you clicked anywhere on the screen it was like pressing the cancel button. We are releasing a new version of our software very soon. At the last minute we decided to remove the "cancel" button but still have the functionality that if you clicked anywhere on the screen you'd be prompted if you wanted to cancel or not. Basically we wanted to hide the cancel button so that the process could still be cancelled but only after we advise them to do so.
>
>Since we are releasing right away I didn't have time to redo the form properly so we decided to make the cancel button invisible. By the way, I found a way around my outline problem. I made the button really small so all you could see would be a small dot. I then moved the command button so that the dot was right on top of a period on some text of the form. Very kludgy, I know, we'll fix it better in the first maintenance release.