Could it be that somehow you have an Override of the normal Messagebox()?

I know that that is possible, but don't remember how. Could that be the source of the problem?

Hi Eti ;

  AFAIK (and see) the MB() command is still super fast on my W10 test PC's.

  In order to help you more though, we would need to know a lot more about your PB edition/version, O/S version, environment, etc.

Regards ... Chris

Greetings, Eti - 

Since you have looked at performance/timing data, can you please provide us with some numbers as to what "relatively longer" means?

I'm curious...Does the measured timing you are seeing include the delay that it takes the user to respond to the message - To click on a response button and close the MessageBox window? If so, those "performance" numbers are essentially meaningless. You might be chasing a problem that is really not a problem.

Regards, John

The MessageBox() function has the effect to grab the focus so that LoseFocus in a Control and/or Deactive Event in a Window are triggered.
If you code for example a sleep(5) in a windows deactivate Event... the message box shows up after 5 seconds.

And ... to answer your question:

The alternative to messagebox() does exist: you create a small response window and pass your info to that one.

How slow is MessageBox function if use create completely new app with NO code at all but this code in its Open event?

// NOTE: Time between first and second dialog tells how fast MessageBox opens
MessageBox("Intro", "Press [OK] to close this dialog and begin the test.")
MessageBox("Test!" "How long did it take from you hit [OK] until this message displays?")

You will sometimes see slow behavior when:

1) User runs app via some terminal services where local printers are shared with terminal app.

2) Your app hasn't deployed the UI Theme files.

RE (2): This happens even when your app doesn't use UI themes. Presence of these files may have tremendous performance impact.

HTH /Michael