creating a custom Message Box

[frankleggett]

Hi

I want to create a Custom Message box where the label and buttons have variable text in them.
I need to run a subroutine that calls the message box and if the answer is yes does 1 thing and if it's no it does nothing.
The problem is I can't get the subroutine to wait for the answer from the other form.
Can someone guide me as to how to load the form get the result and feed the result back to the main form subroutine.
By the way the Message Form as txtlabels and commandbutton labels defined as variables which work fine.

Frank

[frankleggett]

I thought I would add this to make sense of my question.

Form1
Subroutine sets the caption for the message form i.e. "Are you sure"
Sets the name on the buttons for the message form i.e. "Yes" or "No"

The problem is when I press the "No" button on the Message form I want to return to the subroutine that called the message form and use the answer to carry on in the first form

I hope this makes some sense.

Frank

[frankleggett]

I have found the solution using the CallByName function.

[Killer42]

I have found the solution using the CallByName function.

I'm not familiar with CallByName, but had I read your question earlier I would have said to show the message form modally. In other words (VB6 code)...

MessageForm.Show vbModal

This doesn't allow control to return until the form is closed (or hidden, I think).

[frankleggett]

Thanks for you note I might need it latter on in the project. I wanted to go back to the same sub because I was creating a variable which had the name of a procedure. In other words if the answer was yes the variable would have the name of procedure 1 and if no the variable would have the procedure name 2. As I needed to have a lot of these Message Boxes for a lot of different procedures I didn't want to use loads of Message Box forms. Instead I was able to set the name of the procedure in a variable call the message box form call a result procedure in the orginal form and with the CallByName procedure able to call the next procedure using a variable instead of the specific procedure name. CallByName works like this
CallByName object where the procedure is, variable containing name of the procedure, vbMethod
I hope this helps someone else.

Frank

[Killer42]

Thanks for that, Frank.

Glad to hear you resolved your problem. And yes, hopefully this will be a useful addition to the great storehouse of information here at TheScripts. (I know I'll be filing away the CallByName to have a look at when I find the time.:))