Can a MsgBox-like popup be built using an Access form?

[AnotherJob]

I’ve been told that it is easy to make a popup dialog using Access an form, but I have found it impossible. I want my popups to accept passed parameters (not globals), halt all execution until finished, and then return a value (again not via a global). Also they have to work more than once, for example a pick list that may need to pop up many times.

The VBA MsgBox is a perfect example of the popup behavior I desire. It accepts parameters and halts all program operations until the user clicks on a button. Is there anyone here who can point me to an example of how to do that simple thing? Thank you in advance.

[BradHodge]

I’ve been told that it is easy to make a popup dialog using Access an form, but I have found it impossible. I want my popups to accept passed parameters (not globals), halt all execution until finished, and then return a value (again not via a global). Also they have to work more than once, for example a pick list that may need to pop up many times.

The VBA MsgBox is a perfect example of the popup behavior I desire. It accepts parameters and halts all program operations until the user clicks on a button. Is there anyone here who can point me to an example of how to do that simple thing? Thank you in advance.

Change the PopUp property on the form to Yes. This will give you the required aspect you are looking for. Then you can add combo boxes or whatever you wish to to collect the data.

Hope that helps.
Brad.

[FishVal]

I’ve been told that it is easy to make a popup dialog using Access an form, but I have found it impossible. I want my popups to accept passed parameters (not globals), halt all execution until finished, and then return a value (again not via a global). Also they have to work more than once, for example a pick list that may need to pop up many times.

The VBA MsgBox is a perfect example of the popup behavior I desire. It accepts parameters and halts all program operations until the user clicks on a button. Is there anyone here who can point me to an example of how to do that simple thing? Thank you in advance.

Actually this may be done more or less easily and in a pretty elegant manner via OOP.
For example you design a form which represents dialog interface - controls, themes etc. When you write a class which instantiate this form inside itself and make all black job of tuning the form and retrieving the form output. Outside the class everything looks pretty nice and clean - your code instantiates the class object and works with it through properties/methods/events like with some built-in dialog, e.g. Office.FileDialog.
This provides even better functionality than simple getting/returning MsgBox.
Hope this makes a sense.

[AnotherJob]

Actually this may be done more or less easily and in a pretty elegant manner via OOP.
For example you design a form which represents dialog interface - controls, themes etc. When you write a class which instantiate this form inside itself and make all black job of tuning the form and retrieving the form output. Outside the class everything looks pretty nice and clean - your code instantiates the class object and works with it through properties/methods/events like with some built-in dialog, e.g. Office.FileDialog.
This provides even better functionality than simple getting/returning MsgBox.
Hope this makes a sense.

Yes that's what I want to do, but I haven't found a parameter-passing mechanism that works. Can you please post a tiny example, perhaps emulating the MsgBox popup? I'm looking for how to pass parameters to the form before it becomes visible, halt the calling code's execution path until the user dismisses the form, and then retrieve the form's values.

I've tried using

DoCmd.OpenForm MyForm.Name,,,,,acDialog,OpenArgs:=MyArgs

without real success.

If there is a way to pass in the address of the calling object through OpenArgs then I could have the form read and set the calling object's members, but that doesn't seem possible.

[FishVal]

Ok.
I will post a relevant example.
You may also take a look at this thread.
Calling Subroutines across Forms (non-module)
This is actually not the same what I mention but a half way there.