CompuServe Thread

>>Simple misunderstanding of what the Visible property is controlling. This control >>makes the _animation_ visible or not. Not the control itself. Try this test. I double checked & here's how it goes: there are 2 related properties: 1)the HideAnimation property toggles the animation visibility on/off while leaving the control visible on screen 2)the Visible property makes the whole control appear/disappear however, Visible has a pecularity, suppose we set up a form as you suggested with a running animation and a button that does something like: Command1_click Animation1.visible = not Animation1.visible End Sub now if I Set Visible = False at design time and run the program, a break in Command_Click will show that Visible has mysteriously changed to true. but if you check in form1_load the value is still false, which means that it changes somewhere in between.( the Form_load and the command_Click) and now the strangest thing, if you add this line to form_load : — Animation1.visible = false it remains false when you get to Command1_Click, even though theoretically the "Animation1.visible=false" command did nothing!!! my guess is that the value yielded by QuickWatch is a neglected copy maintained by VB , while the actual value is kept in the DLL and is changed by the property assignment. what a fascinating world we live in… Dror.