Thread: [Solved] Declaring a variable that is known across modules
View Single Post
 
Old 11-18-2015, 12:34 AM
Officer_Bierschnitt Officer_Bierschnitt is offline Windows 7 64bit Office 2013
Advanced Beginner
  
Join Date: Oct 2015
Posts: 87
Officer_Bierschnitt is on a distinguished road
Default
Quote:
Originally Posted by shg View Post
You don't need a separate module, but it's a good idea. Just declaring them as Public is sufficient to make them visible throughout the project.

You just can't have another variable more local in scope with the same name.
I'll try. One project can encompass several modules, can't it? I was getting some error_messages in the 2nd module yesterday which led me to believe that my variables - already declared as PUBLIC in the 1st module - were not recognized there. Might have been something different, I'm still not very advanced.

Thanks a lot!

Best regards,

DataNibbler

P.S.: How would I have to do this with a separate module? I haven't found a specific How-to for this. Does there have to be a Sub() in there with the CALL-command for the next module?
Reply With Quote