Your concern should not be whether or not you annoy me, which I'm sure it isn't. Your concern should be whether you're writing good code, which I'm not sure is the case.
My concern is that the code I write is effective, and when possible efficient. I write code as an interesting hobby and the code I write is for no one but me. My code being, "good" is not a factor, or a requirement.

It should be fairly easy to infer from the rest of the post but you could always spend 30 seconds with a search engine to find out.
If what you state is true then I would not be wasting my time trying to cajole occasionally useful information from you.

You should. Even if it's one that I don't like, you should determine what you think is a good convention and stick to it. Consistency is important when writing code. If you do the same thing in multiple places to mean two different things or do different things to mean the same thing then that's a great way to create confusion. It's easy to confuse yourself even, if you put some code down for a while and pick it up later. We've all been there.
What you say is true. However, I would also suggest to you that I am merely a hobbyist and do not have the time or resources to spend learning all of the current jargon and/or the numerous, and often confusing, conventions.

You said that it was a TextBox, so that's what misled me. That said, it should be very rare that you use a Label for a password. Entering a password into a TextBox is one thing but a Label is for display only. Passwords should pretty much always be masked by default, which is why a TextBox has that ability built in. Displaying a password in clear text by default is a security risk. Using a Label for storage rather than display is an abuse of a UI element.
Sorry if I confused you. There is a label, lblEmployed, There is a checkbox, chkActive, and all of the rest are textboxes.

Having said all of that, and after spending a couple of hours digging through some old material I had, it became clear to me that, in spite of your unwillingness to clearly state what was wrong, you had indeed provided the answer to the problem and that it was indeed the fact that the parameter, @recno was in the wrong order and should have been the last parameter and not the first. I suppose you were just providing me with a, "teaching moment". While I find teaching moments to be irritating, that is fair enough.

However, there was an additional problem and that was with the two date fields that required update. I handled that, rather poorly, in the following manner.

Code:
    Private Sub AddParams()
        BldCmd = ""
        MasterBase.AddParam("@firstname", txtFirstName.Text)
        MasterBase.AddParam("@midname", txtMiddleName.Text)
        MasterBase.AddParam("@lastname", txtLastName.Text)
        MasterBase.AddParam("@department", cboDepartment.Text)
        MasterBase.AddParam("@jobtitle", txtJobTitle.Text)
        MasterBase.AddParam("@description", txtJobDescription.Text)
        If Not String.IsNullOrWhiteSpace(txtEmployed.Text) Then
            MasterBase.AddParam("@hire", txtEmployed.Text)
            BldCmd += "Hire=@Hire,"
        End If
        If Not String.IsNullOrWhiteSpace(txtDischarged.Text) Then
            MasterBase.AddParam("@term", txtDischarged.Text)
            BldCmd += "Terminate=@term,"
        End If
        MasterBase.AddParam("@user", txtUser.Text)
        MasterBase.AddParam("@pass", txtPassword.Text)
        MasterBase.AddParam("@active", chkActive.Checked)
        MasterBase.AddParam("@recno", lblEmployeeID.Text)
    End Sub
Code:
    Private Sub UpdateRecord()
        MasterBase.MasterBaseQuery("UPDATE empEmployeeInformation " &
                                   "SET FirstName=@firstname,MiddleName=@midname,LastName=@lastname," &
                                   "Department=@department,JobTitle=@jobtitle,JobDescription=@description," &
                                   BldCmd & "UserName=@user,Pass=@pass,Active=@active " &
                                   "WHERE EmployeeID=@recno")
        If NoErrors(True) = False Then Exit Sub
    End Sub
I am not particularly happy with this, but it is effective. It is unlikely that it is even close to efficient. As for good, I would not know.