Gary,

The _Screen.LockScreen locks _Screen window, not your form. Internaly it uses LockWindowUpdate WIN API.
You can position the form of the screen by setting Top or Left properties to a big enough negative nubmer,and perform all the modifications and than show ready form to a user.

>I have a form with one container on it, at run time a lot of objects are added to the container. Their size is related to the form and container.
>
>I therefore wanted to maximum the form before adding the objects so that they are only resized once (otherwise they would get resized in their own init event and also on form resize).
>
>However if you maximise a form which is not visible then the .resize() event does not fire and height/width are not amended so I have to maximise in the .Activate() event.
>
>This means you get a flicker on the screen as the form resizes. I can then hide it so the user does not see all the objects being added but it pretty yucky.
>
>I thought the _Screen.LockScreen would "lock the screen" and therefore the user would see nothing until _Screen.LockScreen=.F. but it does not, form still appears.
>
>I have also tried using;
>DECLARE INTEGER LockWindowUpdate IN Win32API INTEGER nHandle
>LockWindowUpdate(_VFP.HWnd)
>...
>...
>LockWindowUpdate(0)
>
>But I still get the flicker.