>>If this is something you need on several forms, why not add an invisible editbox to your form subclass? When you need it, you fill it with data and make it visible.
>
>Forms are created dynamically from database and VFP scripts from database are executed on data entry.
>I'm looking for a quick hack for one customer by creating specific script for him. Other customers dont need it, so same exe can used by large number of users.
>
>If proper calculation cannot determined, after that I can try your editbox solution. This requires a more coding compared to one line wait window command. New exe file should probably created and deployed for this customer.

In that .prg you can define an editbox class and a little intro code which will instantiate it on the current form - something you can plug somewhere in form's init or postInit() if you have such a place. The code should measure the form and find an appropriate location on top right, then bindevent() its code to show, hide, update content to wherever you want it and you're done. You may also use a label instead, so it doesn't look disabled (and you can fiddle with properties to give it border etc).

Not as elegant as wait window noclear, but even if you manage to put it where you want it, if the user moves the form, the wait window will stay - it's bound to the _screen, not to your form. Also, I don't know what would happen if there was another form and the user moves that form. I guess it would go under your wait window.