Can I define a module so that it becomes global?
(i.e. No need of Var1 = Module1.Sub1)
Any help would be appreciated.

Edwin

If the module functions or subs are public then they are global by default.

Max Bolingbroke

There are different types of modules, for example, form modules, usercontrol
modules, class modules, and standard modules.  Which one are you talking
about?

Mike

If you are talking about class modules, you could use a class in an
ActiveX DLL with the class Instancing property set to GlobalMultiUse,
adding a reference to the DLL in your main application.

John...............

I think it would be better if I clarify my idea. By a module I mean a simple
module [extension .bas] (not class, not usercontrol). By global I mean
global throughout the project. Suppose I am running a math program with many
functions kept away in a module, I do not want to type ModuleMath,
ModuleMath, ModuleMath again and again. This is my problem. Can anyone help
me?

Thanks
Edwin

Hi Edwin:

The only time you need to qualify as procedure with it's module name is when there is more than one module that eposes the same
procedure.
For example, if you have two modules; Mod1 and Mod2 with the Test() procedure:

'Mod1
Public Sub Test()
End Sub

'Mod2
Public Sub Test()
End Sub

You would have to qualify with Test() you wanted to call:

Call Mod1.Test()
Call Mod2.Test()

If Mod2 did not exist, or there were no other modules that exposed a Test() procedure, then you could simply call the sub:

Call Test()

Hope this helps,

Doug.