I do not understand why you need to declare this object twice, and since I'm writing primary on VB, I try to simulate your situation. Because I do not have your object installed, I make tests with ADO library.

So, I create new C# application and have this Load event for Form1:

private void Form1_Load(object sender, System.EventArgs e)
{
	ADODB.ConnectionClass adocnnTest;
	try
	{
		adocnnTest = new ADODB.ConnectionClass();
	}
	catch
	{
		MessageBox.Show("Error", "Error: Missing Required Files", MessageBoxButtons.OK, MessageBoxIcon.Stop);

		return;
	}

	adocnnTest.ConnectionString = "bla-bla";

}

This code compiles and works fine. What I said was that you have declaration of the same object in another place. Just remove that second declaration - if you use object only in this procedure, declare the object into it, as I do in my example. If you use object also outside of the procedure, move local declaration to the class scope (outside of the Load in my example) - this will guarantee that you can access object also from another procedures.