Why is window "Macro" shown when I try to run a simple code?

[magnusstefan]

When trying a very basic thing taken from "Access 2013 Programming from examples..." something unexpected happens. This is the code:

 Sub ShowMessage()
    MsgBox "This is a message box in VBA."
End Sub

Really basic. When executed a msgbox should be shown: This is a message box in VBA. Instead a window named "Macro" is shown, and there is the name of the macro, and if I push the button"run" the code is run and the Messagebox is shown. But according to the instructions, this "Macro" window should not show up and interfere. What can be wrong?

Also, if I try to enter more code (more subs) this Macro window comes back when I try to execute, and then I cannot only choose the first subroutine!
Same question again: What can be wrong?

[June7]

Where are you calling the Sub from?

[Missinglinq]

And how?

Instead a window named "Macro" is shown, and there is the name of the macro

What is the name of the Macro?

Linq ;0)>

[magnusstefan]

June7 and Missinglinq: This is how the situation looks:

[June7]

I just did a test trying to replicate the issue. Can't. MsgBox opens just fine.

However, the treelist in the Projects pane seems to be missing some lines. Here is what mine looks like.

Note the Modules folder icon and module listed below it.

If you want to provide db for analysis, follow instructions at bottom of my post.

[Missinglinq]

That link craps out, June7...saying that it is an invalid attachement.

Once again, magnusstefan, exactly how and from where are you calling the Sub?

Linq ;0)>

[June7]

Interesting, just opened for me. It was supposed to be embedded not a link. Will try to fix.

Looks like they are calling sub from immediate window for testing.

[Missinglinq]

I wondered if the OP was calling it by typing ShowMessage in an Event, like maybe the OnClick event, in the Properties Pane. That might fool the Access Gnomes into thinking that ShowMessage was the name of a Macro.

Linq ;0)>

[June7]

Just tested for that. All I get is an error message "cannot find the object", not the Macro dialog.

Oh, and I just noticed the Immediate window shows different procedure from the Macro dialog popup.

Think we need the db to figure this one out.

[HiTechCoach]

Make sure that you do not have a macro with the same name.

Also try:

Call ShowMessage2 "I am learning VBA"

and

Call ShowMessage2("I am learning VBA")

TIP: Add the line Option Explicit after the line Option Database...

[Missinglinq]

Of course, there's always the possibility that corruption is involved, here!

Linq ;0)>

[magnusstefan]

Chap01.accdb This is the actual database!

Further explanation: This is the first exercise in the book "Microsoft Access 2013 programming with examples", and the screen shot in the book looks exactly as in my practicefile. You see, the only thing "done" with this database is:
1) Creating it as a blank database called "Chap01".
2) Selecting the database Tools tab clicking on "Visual basic."
3) Inserting a standard module by choosing "module" from the insert menu.
4) Entering the code.

The first code works just fine (Sub ShowMessage()
MsgBox "This is a message box in VBA."
End Sub)

But not the second (Sub ShowMessage2(strMessage)
MsgBox strMessage
End Sub)
if tried, the mysterious "Macro window" is suddenly there...

[magnusstefan]

"Once again, magnusstefan, exactly how and from where are you calling the Sub?"

Please look at screen shot in post number 4!

If that does not answer your question, please explain further what information you want!

[magnusstefan]

Sorry, I just do not understand your answer!

"Make sure that you do not have a macro with the same name."
With the same name, as what?!

[June7]

Don't want macro to have same name as VBA procedure.

Since there are no forms or reports, the only place to call from is another Modul1 procedure or the immediate window. Calling both subs from immediate window works just fine.

So why does your image have ShowMessage2 in the immediate window but the macro popup is for ShowMessage?

Where exactly are you calling ShowMessage that provokes the popup? If you are trying to reference the sub in a Macro, then be aware macro cannot call Sub, only Function. Change the procedure to a Function. And when you call it, don't forget the ().

ShowMessage()

However, since there are no macros in the posted db, still can't explain why you get the macro popup.