Create Function that can be called from VBA on any form.

[ts_hunter]

Correct me if I am wrong, but each form has its own block of VBA code within an Access application.

What I want to do is create an e-mail function in my Access Application that I can pass address, subject line, and message to and have it use CDO to send the SMTP message to my mail server. I have found the correct CDO e-mail code, but I am wondering how (if possible) to create on callable function in my Access project that can be called from any form, so I don't have to put the same e-mail code in each form {like to keep things clean if I can}.

[June7]

Yes, forms and reports can have associated code modules.

The application also has general modules. This is where you want the generic procedure.

Build the function or sub with arguments. What those arguments should be depends on your requirements. Wherever the function is called from, pass the appropriate values with the arguments so the function has required information to execute properly. You mention 3 arguments, so something like:

Sub SendEmail(strAdd As String, strSub As String, strMsg As String)
'code to send email
End Sub

Call the procedure from form module:
Sub btnEmail_Click()
SendEmail("toAddress", "subject text", "message text")
End Sub

[ts_hunter]

In my project when I am in the VBA programming area, I right click and select Insert... I have the option of Class Module and Module. Which of these is the global one that can be called from anywhere in my project?

[June7]

I think either can but I have never used Class Module.

[ItsMe]

If you just want to create a public function use a general module. That would be, "Module". A class module is associated with a class. For instance, forms are a class and they have class modules. You do not see their class modules in the area you are looking. They are listed with the forms. Class modules in the section you are for objects that you create and define or instantiate. An object that is created via VBA will have a name and you may want some code to fire when that object is used/created or even when your code is finished with the object. You could have a class module associated to this object by name.

PS I have used class modules but I have never bothered to create them myself.

[Missinglinq]

Note that when prompted to name the Module that your Function resides in, name it anything except the same name as the Function; doing that irritates the Access Gnomes no end, and they'll throw error messages at you, to show their displeasure!

Linq ;0)>