I'm deep in WPF at the moment so can't remember (and can't check) but will executing a .Close() in the OnLoad override do the trick ?
(can be before or after base behaviour)

>From "maintask" I "new" the form and then ".show" it (are there any other ways? :) . The code to determine if the form shoulld open or not is in ".load" (it basically checking if the user has access, but there could be other uses for this functionality).
>
>I could of course write that code in maintask, but I was hoping to encapsulate the logic in my "base" class.
>
>Thanks for caring.
>
>
>
>
>
>>>In VFP, when you return .f. in the .init routine, the form did not come up at all.
>>>
>>>What would be the "best practice" equivalent in VB.NET, preferrably without the form flashing? I'm issuing a me.close in the layout event, but that flashes.
>>>
>>>Thanks of any light you could shed on this.
>>
>>How are you instantiating the form?
>>
>>At what point do you know that you don't want to do that ?