Design issues, tendency to write custom methods
Just a few small notes:


The method has seven parameters which isn't a good smell. Maybe some of them could be class field.
First, I'd reverse some conditions and use guard clauses to make the code flatten.

for (int i = 0; i &lt; dtSProcList.Rows.Count; i++)
{
    if (dtSProcList.Rows[i][0].ToString() != cbSProcList.SelectedItem.ToString())
    {
        continue;
    }

    string temp = dtSProcList.Rows[i][0].ToString();
    if (dtSProcList.Rows[i][1] == DBNull.Value)
    {
        //Returns control to calling method if the parameter name is null.
        return;
    }

    inputLabels[counter].Text = dtSProcList.Rows[i][1].ToString().Remove(0, 1);
    inputLabels[counter].Visible = true;
    inputLabels[counter].Enabled = true;
    inputTxtboxes[counter].Visible = true;
    inputTxtboxes[counter].Enabled = true;

    selectedSProcInputs.Add(inputTxtboxes[counter]);
    selectedSprocDataTypes.Add(dtSProcList.Rows[i][2].ToString());

    counter++;
}


References: 


Replace Nested Conditional with Guard Clauses in Refactoring: Improving the Design of Existing Code; 
Flattening Arrow Code

0, 1 and 2 are magic numbers. Using named constants instead of numbers would make the code more readable and less fragile.
What does the counter count? You should give it a name which shows the intent of the variable.
dtSProcList.Rows[i] repeats five times in the code. A named local variable could remove this duplication.
The temp variable seems to be unused. If it's superfluous remove it.