Using ONE Module With All Data Connection And Recordset Opening And Closing Options

Finally starting some coding in VB.Net, I notice over the years, that we can say (in VB6)

Code: Dim MyForm_Stock as NEW frmStock

in the same session, being able to open, say 3 Stock Forms at the same time and maintain details independently of each of the other forms. Also am I able to maintain separate Database connections and the same table being opened and updated independently of each other by each separate form. What is actually taking place in terms of memory being used by each process? My ultimate goal is to be able to have ONE Module with all the possible data Connection and Recordset Opening and closing options, which I have failed miserably to do in my VB6 experience. Data access is an obvious module based set of subroutines. Others could be Date routines eg, Week Number of the year, Days Diff, Days to, etc. [Code]