0

I have an old VB6 application which I am reworking to VB.NET and the previous programmer set this sort of thing when validating MaskedTextBox components:

MsgBox("My message")
b = True
myField.Focus()

Basically, a message box is open and if the validation failed the focus should get to other myField text component.

I changed the Enter event to GotFocus and now when the validation fails I am stuck on the current text field forever. I cannot even close the window because of the constant message box that appears.

I fixed the problem on GotFocus by moving the other statements above the MsgBox() command.

Yes it works well now, but really want to understand how does MsgBox affects the execution of the program?

Vlad
  • 2,739
  • 7
  • 49
  • 100
  • 1
    `MsgBox` will halt execution until an action has been selected, which is helpful when you want to be getting `DialogResult` from one, for example asking a questions and retrieving a Yes or No value. – Sasha Oct 06 '17 at 13:18
  • Please use the right tags. There is no VB6 question here, and porting code to a different language is not an "upgrade." – Bob77 Oct 07 '17 at 03:40

1 Answers1

1

From MSDN:

Displays a message window, also known as a dialog box, which presents a message to the user. It is a modal window, blocking other actions in the application until the user closes it. A MessageBox can contain text, buttons, and symbols that inform and instruct the user.

I can only guess it was either used for debugging or to give out an error message to the user.

If it was for an error message this might help: Call MessageBox from async thread with Form1 as parent

David Sdot
  • 2,343
  • 1
  • 20
  • 26
  • It is mostly used for validating input data, so no debbuging purposes. I now use Try/Catch for debugging. Should I still use MsgBox for validating data or there is a better approach? – Vlad Oct 06 '17 at 13:28