I think I am following you now, and is pretty much what I thought you
were looking for.

Well, if you are new to OO design, not to worry.  The days of having to
create little classes for stuff sort of came and went (at least for
VB2005) for data storing/displaying.  I create a custom class for stuff
like printing.  As for collection objects, I haven't used one for a few
years now.  I store data in datasets/datatables which can be available
as much as you want - depending on how much scope you give your dataset.
Ex:

----------------------------------------------
Imports System
Imports System.Data.SqlClient

Public Class Form1
Dim da as SqlDataAdapter, ds As DataSet
Dim conn as SqlConnection
Private Sub Fomr1_Load(...)Handles...
conn = New SqlConnection
conn..ConnectionString = "Data Source=yourSvr;Initial
Catalog=yourDB;Integrated Security=True"
ds = New Dataset
da = New SqlDataAdapter
da.SelectCommand = New SqlCommand
da.SelectCommand.Connection = conn
da.SelectCommand.CommandType=CommandType.StoredProcedure
da.SelectCommand.CommandText = "yourSP"
da.Fill(ds,"tblSteve") '--tblSteve gets created on the fly
'--now populate a datagridview control on your form
datagridview1.Datasource = ds.Tables("tblSteve")
End Sub
----------------------------------------------

In this sample I made the dataset at the Form level.  So
ds.Tables("tblSteve") will be alive as long as Form1 is alive.  And
tblSteve will contain whatever rows/columns your SP contains/returns.
And these can be automatically displayed in a datagridview control (much
easier to deal with and way more flexible than a Listview control).

Well, this is my suggestion.  

HTH

Rich