>It's not that it's *wrong*, meaning it won't work ... but since it's not necessary to do, then it's simply redundant and I doubt if it makes it any clearer to the developer as to what is going on.

Ok, let's try this code:

        Public lLogin As Boolean = False
        Public lSave As Boolean = True
        Public nErrorValidation As Integer = 0
        Public nPrimaryKey As Integer = 0
        Public nSQLMode As Integer = 1
        Public oApp As Framework.App = New Framework.App
        Public oDataProvider As Framework.Data = New Framework.Data(oApp)
        Public oDropDownCondition As Collection = New Collection

To me, it is much easier to understand the declarations when everything is declared the same way.