Expected variable or procedure, not module [closed]

Question

Closed. This question needs to be more focused. It is not currently accepting answers.

Want to improve this question? Guide the asker to update the question so it focuses on a single, specific problem. Narrowing the question will help others answer the question concisely. You may edit the question if you feel you can improve it yourself. If edited, the question will be reviewed and might be reopened.

Closed 5 years ago.

Improve this question

I have been trying to sort this error and can't understand why it is happening. tried changing name of the sub and check many times to make sure the spelling is exactly the same but the error keeps ocurring and i can't understand why. Can someone help?

Please read: • An image of your code is not helpful and • Why is “Can someone help me?” not an actual question? • Then edit and improve your question. — Pᴇʜ
– Pᴇʜ, Commented Mar 12, 2020 at 10:16
To call a method in a standard module: ModuleName.MethodName — Kostas K.
– Kostas K., Commented Mar 12, 2020 at 10:20
I did read - learn.microsoft.com/en-us/office/vba/language/reference/… -help/expected-variable-or-procedure-not-module and ozgrid.com/forum/index.php?thread/… - stackoverflow.com/questions/2804327/… and some other links i managed to get from searching google for the error but was unable to actually understand it and still not understanding. "Can someone help me" is my way of saying "can someone help me understanding what am I doing wrong" — rsg
– rsg, Commented Mar 12, 2020 at 10:32

Pᴇʜ · Accepted Answer · 2020-03-12 10:33:46Z

2

You should not use the same name the module and the procedure. This will cause a conflict.

So if you Call SortDataSource it will find the module name first and of course it cannot call a module (only a procedure or function within a module).

So if you use the same names you need to Call SortDataSource.SortDataSource to make it call the procedure SortDataSource inside the module SortDataSource:

Syntax is like

Call ModuleName.MethodName(Argument1, Argment2)

or without Call which is not needed.

ModuleName.MethodName Argument1, Argment2

But I highly recommend not to use the same name for a module and a procedure. As you can see it can cause errors that can easily be avoided by choosing different names.

edited Mar 12, 2020 at 10:33

answered Mar 12, 2020 at 10:20

Pᴇʜ

57.9k10 gold badges55 silver badges75 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Nemoko Over a year ago

Quick question, doesnt ModuleName.MethodName Argument1, Argument2 give an error? shouldn't it be ModuleName.MethodName(Argument1, Argument2) Not tryna be rude or anything. was just wondering :)

Rory Over a year ago

Yes, if using Call then the brackets are required.

Pᴇʜ Over a year ago

@Rory arrrg yes of course! I never use it. Thanks for pointing out.

rsg Over a year ago

Thank you. so why does it work when i use the other call without specifying method name "Call RowDelete" but it does not work with "Call RowSort" and I have to do the Call ModuleName.MethodName Argument1, Argment2 for that one?

Pᴇʜ Over a year ago

@RubenGaspar Don't get your question. What exactly works and what doesn't? Please be more precise. If you need to post more code please edit your original question add the code there and leave a comment.

|

Collectives™ on Stack Overflow

Expected variable or procedure, not module [closed]

1 Answer 1

7 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

7 Comments

Linked

Related