>Hi George,
>I just saw you refering to a FAQ in a different message. Those undocumented messagebox parameter values sounds very neat. I've just got a couple of questions regarding those parameters.
>
>

>#DEFINE MB_SYSTEMMODAL 4096
>#DEFINE MB_TASKMODAL 8192
>

>
>It says that mb_SystemModal doesn't produce any noticable effects but it causes internal differences. Do you know what those internal differences might be?
>
>I am using vfp7 and W2K. When I execute:
>

>messagebox("Hi there",MB_SYSTEMMODAL,"Test")
>

>it brings the messagebox dialog to the top over all applications. According to the FAQ it should be mb_TaskModal that does this. Should the two numbers switch places?
>
>Has anybody had any problems using these undocumented messagebox parameter values in any application?
>
Einar,

As I stated in the other thread, I wrote that some time ago and haven't tested it since. At the time, I was probably running VFP 5 or 6 under Win95/98. So it's quite possible that some behavior modifications in the underlying OS have occurred.

AFAIK, MB_SYSTEMMODAL is a holdover from Win16 where you could create system level modal dialogs. Under Win32, you can't. However, if MB_TASKMODAL no longer performs as stated, then it's time to update the FAQ.< s >

I would seriously doubt that any problems would be caused by using these parameters. As should be obvious, VFP's MESSAGEBOX() function simply calls the API function of the same name. In fact, the information that appears in the FAQ was gleaned from the documentation of the function in the Platform SDK.