Why Does Macros Dialog Pop-Up When I Try To Run Code In VB Editor?

[Soule]

I'm trying to see if the following frustratingly simple code runs to open Outlook:



Private Sub A1S1_Form_Re_send_Welcome_E_Mail_Only_Button_Click ()
Dim objOutlook As Outlook.Application
Set objOutlook = CreateObject("Outlook.Application")
End Sub

But when I hit the "Run" arrow button in the toolbar, the "Macros" dialog box pops up (with no entries). Why is this happening and should I be entering something in it?

The button that this code is for is an On-Click "Event Procedure" event. I thought that in 2007, that was code and not a macro.

Why can't I do a simple step-compile in the editor, Microsoft?!

Much thanks ahead of time for any advice,
Frank
Windows XP, Access 2007, .accdb file

[June7]

It's because the Sub not in a general module. VBA can't find it so prompts with the Macro dialog. You can call form subs from immediate window by referencing the form.

Form_formname.A1S1_Form_Re_send_Welcome_E_Mail_Onl y_Button_Click

[Soule]

It's because the Sub not in a general module. VBA can't find it so prompts with the Macro dialog. You can call form subs from immediate window by referencing the form.

Form_formname.A1S1_Form_Re_send_Welcome_E_Mail_Onl y_Button_Click

Thanks, June! I cut/pasted the code into its own module and named the module to "Re-Send Welcome E-Mail Only Button" for clarity. The code building area in the main form is now blank, except for the declarations.

Is there any problem with the way it is now?

[June7]

Okay, you can have code in a general module. How do plan to run it? Always by manual execution? Or have the button click call the sub?

[Soule]

Okay, you can have code in a general module. How do plan to run it? Always by manual execution? Or have the button click call the sub?

What is the difference?

I want it to run when the user clicks on a form button...

[June7]

That is fine unless you need to refer to controls on form for some data. If the code were behind the form could use Me.control name. With code in general module will have to pass values as arguments of the sub or have sub get the values by reference to the form: Form_formname.controlname.

[Soule]

Okay, you can have code in a general module. How do plan to run it? Always by manual execution? Or have the button click call the sub?

What is the difference between manual execution and having the button click call the sub? Aren't they the same thing?

[June7]

By manual I mean position the cursor in the procedure and click Run. I have a few maintenance/utility procedures only I run, no need to make available to other uses and I never bothered to build accessibility in forms. But you have button dedicated to this so all good.

[Soule]

Thanks, June -

I'm going to take your advice and move my on call button code back into the form's main class module so I can use the "Me" function to call data out of controls (which I do actually need to do) instead of always having to type out "[]![]" references in my code. The "Me" code is simpler and I want to keep my code simple.

If the "Macros" dialog box opens while I am compiling in the VB editor, I'll just have to close it every time. No big deal.

[June7]

The macro dialog box should not appear if you test the code by executing it from the button click.