How to run a separate private procedure within the same module

**clemsoncooz** · 02-16-2012, 04:28 PM

I'ver searched and cant find a solution.

Is this allowed?

Are you able to call a different PRIVATE procedure from within the same module?

Ive tried:

Please Login or Register  to view this content.

Where "CheckBox1_Change" is the name of the procedure that I want to call and I get Run Time Error 1004.

**buran** · 02-16-2012, 04:34 PM

Hi you can call it like any other sub, e.g.

Please Login or Register  to view this content.

or

Please Login or Register  to view this content.

buran

**dominicb** · 02-16-2012, 04:37 PM

Good evening clemsoncooz

Sure. Just use the Call command, thus :

Please Login or Register  to view this content.

You could also just use the sub name, for example :

Please Login or Register  to view this content.

Either will work fine.

HTH

DominicB

**clemsoncooz** · 02-16-2012, 04:38 PM

ohhh okay. Thanks!

So is the Application.Run "" for private procedures located in OTHER Modules?

**dominicb** · 02-16-2012, 04:43 PM

Hi clemsoncooz

Not necessarily, other modules, but other modules in different workbooks.
You would use the notation as below :

Please Login or Register  to view this content.

HTH

DominicB

**clemsoncooz** · 02-16-2012, 04:46 PM

Thank You!

**buran** · 02-16-2012, 04:51 PM

I agree that Application.Run is for subs in other project/workbook. It can be used also to run subs from another application, e.g.

Please Login or Register  to view this content.

where wdApp is Word.Application variable and above code is executed from Excel macro.

buran

**clemsoncooz** · 02-16-2012, 04:57 PM

So is it not possible to run a PRIVATE Sub located within the SAME workbook - just in a different module?

I thought "Private" just removes it from the available list of macro's that the user can run with "ALT+F8" (within excel screen - not VBA screen).

**buran** · 02-16-2012, 04:58 PM

My initial statement was incorrect, I edit my post. dominicb is right.

**buran** · 02-16-2012, 05:07 PM

clemsoncooz,
private/public defines the scope of the sub. It's not only about user being able to run it with ALT+F8, but also from where you can run the sub in VBA.
Look at the attached file. in Module 1 you have a private sub. in module 2 there are two subs that try to run the private sub from Module1. One is using call and the other application.run
Actually the project does not even compile because call method does not "see" the private sub in the other module. However the application.run does the job. try to run each of the two with F5/F8 to see the difference.

buran