Hi,

I have a number of variables declared in one module which I need in a second module which is called from the first one.
The variables are all declared using the keyword "Public", but it seems those are global only within one module.
How can I either declare them cross-module-global or just transfer them from one module to the next?

Thanks a lot!

Best regards,

Officer_Bierschnitt



P.S.: I think I have understood what I've found online insofar that I can create another module, call it "Declarations" and there declare all my variables as PUBLIC and they will be global across modules. Right? Do I then have to call my first module from that one?

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?

If you declare a Public variable in a class module (for example a worksheet or ThisWorkbook module) then the variable may only be accessed as a member of that class. Therefore you must refer to it using syntax such as Sheet1.Variablename or ThisWorkbook.Variablename. If the variable is declared in a normal module, you may simply refer to it using its name from any other module in the workbook.

Ah. So, if I've understood you correctly, I have to create a new module in the workbook and declare all the variables as PUBLIC in that module and all other modules will recognize them.

I have already tried that. It seems to work. Let's see.

Best regards,

Officer_Bierschnitt

The reason for declaring them is a separate module is just hygiene. They are not specific to any other module (that's why they're public), and keeping them together lets you find them all at a glance. For someone trying to understand your code, it's a good place to start reading.

Public variables have their place, but should be used only after careful consideration of the alternatives. In general, they can make code harder to debug and maintain.

The only code I might include in that module is a routine that initializes those variables.