>>Steve,
>>1) You could set window of wait to an off screen position.
>>2) You don't need visible=.f. in code (and actually not the recommend way). Instead have:
>>screen=off
>>in config.fpw
>>
>>I don't know why visible = .t. cure it. I suspect a modal state but not sure.
>>PS: Are you sure in both cases you just start the exe and do not touch kb/mouse.
>>Cetin
>
>I will check the off screen suggestion
>
>And I will check config.fpw. The application does need to be seen most of the time. I just wanted a silent switch for third party applications.
>
>In the activate of the form:
>
>IF ThisForm.lExitOnInit
> CLEAR EVENTS
> ThisForm.Release()
> CANCEL
>ENDIF
>
>In my program, I can call 2 forms and not have the same interaction. Later, I wanted to be able to add command in Windows Explorer like Winrar. The command line will be more useful then.

Update:
It seem there is a correlation when _vfp.Visible = .F. and code not being executed in the activate of the form. The "Cancel" code was copied and placed in the init also. It now work. I also changed config.fpw.

My solution: I was able to make it almost "silent" by changing the wait window by my own function. It check the statut of _vfp.Visible.

I also change the coordinate to be outsite of the screen (left 4000, top 4000). I had to do that because was seeing a window for 1/10 of a second. My only remaining trouble is a .2 second showing in the Windows taskbar but found a function that suppossed to hide it. I will have to test that.