Using a class module to create a user input box

[TjabbeTjibsma]

I'm trying to setup an input box that will force the users of an Access DB to enter a (mandatory) comment before they update certain fields. The built-in 'InputBox' function only allows one line of 256 characters to be entered.

I'm looking for a larger, multiline textbox.

After some searching I came across this post:
http://www.dbforums.com/showthread.php?1675385-Make-input-form-bigger-to-allow-for-multi-line-text

This seems to do exactly what I want except for the fact it doesn't work... The problem: after adding all the code and looking for the post for additional instructions, I weeded out all error messages, but there is no pop-up box appearing.

My questions:
1) is anyone here familiar with the approach in the post I linked to? Or perhaps with this very code? If so, can you confirm this still works with access 2010?
2) Perhaps I'm making this too complicated and is there a better way to accomplish an improved / extended version of the default 'InputBox'

I have added a DB of the code to this post, exactly as copied from the instructions in the link.

[Seth Schrock]

That is a very complicated way of doing things. All you need to do is create a form with the controls that you want. Then set the form's Modal and Pop Up properties to Yes. Create a global variable that will store the value that you enter. To open this form, use the following code:

DoCmd.OpenForm FormName:="frmInputForm", WindowMode:=acDialog

In your form's OK button, assign the value that you have entered to the global variable and then close the form. Once the form has closed, then your code resumes at the next line after the line that opened the form. You can now reference your global variable to get the data that you entered.

[TjabbeTjibsma]

One of the reasons this appealed to me, is that you can customize the Form each time you instantiate it. I have to use this popup for multiple fields.

If I understand your solution correctly, I would have to make a specific form for each situation, or precede each popup form with a popup message explaining to the user what to fill out.

[jforbes]

I agree with Seth, there is no need to create a class and deal with properties.

To expand on what Seth has detailed, here is some code I copy and pasted together to accomplish what he's laid out. It allows you to supply the Prompt, Title and a Default Value for the TextBox:

' Placed in a module
Public gMultiLineInputBoxPrompt As String
Public gMultiLineInputBoxTitle As String
Public gMultiLineInputBoxValue As String
 
Public Function MultiLineInputBox(ByRef sPrompt As String, Optional sTitle As String = "MS Access", Optional sDefault As String = "")
    gMultiLineInputBoxPrompt = sPrompt
    gMultiLineInputBoxTitle = sTitle
    gMultiLineInputBoxValue = sDefault
    DoCmd.OpenForm FormName:="frmInputForm", WindowMode:=acDialog
    MultiLineInputBox = gMultiLineInputBoxValue
End Function

' Placed in a Form
Private Sub cmdCancel_Click()
    gMultiLineInputBoxValue = ""
    Docmd.Close
End Sub
 
Private Sub cmdOK_Click()
    gMultiLineInputBoxValue = Me.txtInput.Value
    Docmd.Close
End Sub
 
Private Sub Form_Load()
    Me.Caption = gMultiLineInputBoxTitle
    Me.lblInput.Caption = gMultiLineInputBoxPrompt
    Me.txtInput.Value = gMultiLineInputBoxValue
End Sub

Usage:

SomeVariable = MultiLineInputBox("What is your favorite color?", , "Red")

The trick really is to set the EnterKeyBehaviour Property of the TextBox to "New Line in Field", otherwise the Enter Key will move out of the TextBox and not create a new line.

[TjabbeTjibsma]

Seth, Jforbes,

Thanks both for your quick and accurate replies. With Jforbes addition, this will work for me!

In my implementation I made a small change: instead of using global variables I added the necessary variables to my collection of TempVars.