>Hi dragan,
>
>Thanks for your reply, but I can't help there still is a bug.
>
>See details of my case.
>
>It occurs when SET STATUS ON (as oposed to SET STATUS BAR ON) and only when there is code in the init of the form.
>
>I can't see the relation to your situation below. I'm not using ?? anywhere in my program and SET TALK is set to off, so there should be no output to the form anyways. It prevents the form being instatiated to appear but is listed in the windows menu, while other forms continue to work as advertised.
>
>I can't see why the behaviour should occur with SET STATUS ON and not with SET STATUS BAR ON
>
>It certainly is a bug in my eyes. It was VERY difficult to track on what is going on here.

I've had a few such cases of my own, and I wrote the above just as an explanation of what's probably going on, and why I don't think the problem will go away.

IMO, the bug is not in ctrl+s behavior per se, it's in VFP's use of some system service for console output - which has had this behavior even before DOS. It may have been cleaner if they wrote that from scratch, without all of the historical baggage.

In this case, I think the best you can realistically expect to have is a decent workaround.