>

>Public oParameters As OleDbParameterCollection
>...
>oParameters = oDataAdapter.SelectCommand.Parameters
>

>
>oParameters doesn't sound to be a good naming really.
>
>

>loDataProvider.oDataAdapter.SelectCommand.Parameters.Add( ... )
>loDataProvider.oDataAdapter.UpdateCommand.Parameters.Add( ... )
>loDataProvider.oDataAdapter.InsertCommand.Parameters.Add( ... )
>

>
>PS: Might not be right. Thinking C# wrting VB:)

I am trying to set this up in a class. Once the class is instantiated this is when I initialize the oParameters property. So, I create it like this:

        Dim loDataProvider As Framework.Data = New Framework.Data
        loDataProvider.oParameters.Add(New OleDbParameter("@Username", lcUsername))
        If loDataProvider.SQLExec("SELECT Numero,Password,Session FROM " + tcTable + _
         " WHERE Username=""" + lcUsername + """", tcConnection) = False Then
            Framework.App.nLoginSuccess = 4
            Return False
        End If

so I can have an instance of the class, initialize oParameters property and then call the method.

Why also do you think oParameters is not a good representation of the property name?