Look at this pieace of code:

Option Explicit

Imports System.Data.SqlClient

Module Globals

    Public lConnection As SqlClient.SqlConnection

End Modules

Now I'm trying to refer to "lConnection" in a class called Data.Access which will later be used in my main application. When I Import the namespace as 'Globals' in my Data.Access Class I should be able to access the "lConnection" variable as it is publicly accessible to other classes or am I interpreting it incorrectly?

EricJ

I don't know if this will help at all, but I dug this out of the MSDN documentation after some searching:
Remarks
Modules are a reference type similar to classes, but with some important distinctions. The members of a module are implicitly Shared and scoped to the declaration space of the standard module's containing namespace, rather than just to the module itself. Unlike classes, modules can never be instantiated, do not support inheritance, and cannot implement interfaces. A module can only be declared in a namespace and cannot be nested in another type.

You can have multiple modules in a project, but members with the same name defined in two or more modules must be qualified with their module name when accessed outside of their module.
Source: http://msdn.microsoft.com/library/en...akeyModule.asp

-Peter

Thanx Peter!

I looked at the exact same documentation a while ago, but still face the same problem.

I Visual Basic 6 it was easy to create a new ActiveX DLL, add a module, compile it into a DLL and add the reference, but I'm having huge problems inplementing a similar case in VB.Net.

I copied the Module 'Globals.vb' into every project in my solution and that works fine, but still doesn't allow me to create one instance (it can not be instantiated) of the module and calling it up in my other projects.

I will browse around the net some more!

I also face another problem when creating a new property which should be 'WriteOnly':

Public WriteOnly Property ConnectionProp(ByVal ConnectionString As String)

   Set(ByVal Value)

       m_ConnectionString = ConnectionString

   End Set

End Property

When calling it in the Initialization section of the class I get the following error: "'Argument not specified for parameter 'ConnectionString' of 'Public WriteOnly Property DefaultConnectionString(ConnectionString As String) As Object'"

EricJ

Is there a particular reason you are trying to use a Module? You can do what you are looking to do with a class that has shared members. It will serve the same purpose and probably cause you less headaches.

The property problem is that your signature is incorrect. It should look like this:

    Public WriteOnly Property ConnectionProp() As String
        Set(ByVal Value As String)
            m_ConnectionString = ConnectionString
        End Set
    End Property


-Peter