>It worked when I set the controls as .Visible = .F. and then .Visible = .T.
>
>What a weird thing!?!


Somehow yes and somehow not.

Any ActiveX-control is a complete (standalone) Application mostly written in C.

The whole thing is kind of a trick. You must imagine Your form having a rectangle cut out. the ActiveX lays behind that and "shines through". That's
why You can't put any VFP-Controls on top of an axtiveX - they simply fall in the hole. You can imagine the ActiveX laying on top. The effect would be the same.

So if You issue "This.Container.Visible = .F." and communication between VFP and the ActiveX is not optimal, this might not have an effect on the control. The Control remains in Visible=.T. So if You later issue "This.Container.Visible = .T.". There is no need for the control to do anything, because it has been visible all the time.

Try this :
Add a container to a form and put the Progress-bar into the container. Make the container red or something.

Start the form and issue form.container1.Visible = .F.
The container vanishes, but the progressbar is still there. (if not, You could write ? form.Container1.olecontrol1.Visible and will get a .T.

So if You start Your form in a hidden mode and have the Progress visible=.t. There is no need to change its state later on if You issue the show() method.