Hi Agnes,

>4096 is declared in Foxpro.h as "MB_SYSTEMMODAL", 0 as "MB_APPLMODAL" (what means every MESSAGEBOX needs to be modal to the app).
>Actualy 4096 lost its systemmodal. In the moment I'm writing this a messagebox with value 4096 added is active, VFP 7.0 is blocked but nothing else.
>So we can not set a messagebox modal to the system, what ever this may be good for.

This is what the MSDN lib says: "This flag has no effect on the user's ability to interact with windows other than those associated with hWnd." In Win 3.x systemmodal was something, that really blocked all other apps that were running. Today, systemmodal is applmodal + "always stay on top regardless what app is active".

IMO, adding 4096 is a workaround, we can be glad to know about, even if it doesn't cause the effect we would really like to have (the same behaviour of a messagebox with and without the timeout clause). I don't like a MessageBox being on top of all apps.

>Finaly this seems to be a bug.

IMO, the behaviour of MessageBox with timeout definetely is! It seems, that the window handle of the main VFP window is not passed correctly to the Win API MessageBox function when using the timeout clause.

Regards,
Armin