OleDb Stored Procedure Call Problem

[johndonnelly]

HI,

I am trying to figure out how to write a C# program to add parameter's "A" and "B" and return "C" in the following code:

I get an error at the commnd.ExecuteNonQuery(); statement below. The error states:

X2 Provider Error: <ExecuteHelper Failed>
X2 Provider Error: <Internal Error: Failed to get the IProc Interface>

The provider works with ADO.Net according to the developer.

Here's the code I have so far:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data.OleDb;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Data;
using System.Windows.Forms;
 
 
namespace ADP_API
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
        }
 
        private void button1_Click(object sender, EventArgs e)
        {
            string constr = "provider=ADPProv.ADPProv.1;host=" + Host.Text;
            constr = constr + ";product=" + Product.Text;
            constr = constr + ";server=" + Server.Text;
            constr = constr + ";password=" + Password.Text;
            constr = constr + ";pooling=TRUE";
 
            OleDbConnection con = new OleDbConnection(constr);
 
            con.Open();
 
            OleDbCommand commnd = new OleDbCommand();
            commnd.Connection = con;
            commnd.CommandType = CommandType.StoredProcedure;
            commnd.CommandText = "proc=Addition";
 
            OleDbParameter paramReturnValue = new OleDbParameter();
            paramReturnValue.ParameterName = "C";
            paramReturnValue.OleDbType = OleDbType.Integer;
            paramReturnValue.Direction = ParameterDirection.Output;
 
            OleDbParameter paramA = new OleDbParameter();
            paramA.ParameterName = "A";
            paramA.OleDbType = OleDbType.Integer;
            paramA.Direction = ParameterDirection.Input;
            paramA.Value = var1.Text;
 
            OleDbParameter paramB = new OleDbParameter();
            paramB.ParameterName = "B";
            paramB.OleDbType = OleDbType.Integer;
            paramB.Direction = ParameterDirection.Input;
            paramB.Value = var2.Text;
 
            commnd.Parameters.Add(paramReturnValue);                            commnd.Parameters.Add(paramA); // parameter 1
            commnd.Parameters.Add(paramB); // parameter 2
 
 
 
           commnd.ExecuteNonQuery();
 
            int returnValue = (int)commnd.Parameters["C"].Value;
 
            Output.Items.Add(returnValue);
 
            con.Close();
 
        }
    }
}
 

Thanks,

John

[johndonnelly]

OK I got it to return a value in my listbox with the following code but with 6 and 5 put in for var1 and var2 respectively I get a zero in the list box. Any ideas why commnd.Parameters["C"].Value is null? Could it be that ExecuteNonQuery is wrong for this??

Thanks

Here's my new more successful code:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data.OleDb;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Data;
using System.Windows.Forms;
 
 
namespace ADP_API_Practice
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
        }
 
        private void button1_Click(object sender, EventArgs e)
        {
            string constr = "provider=ADPProv.ADPProv.1;host=" + Host.Text;
            constr = constr + ";product=" + Product.Text;
            constr = constr + ";server=" + Server.Text;
            constr = constr + ";password=" + Password.Text;
            constr = constr + ";pooling=TRUE";
 
            OleDbConnection con = new OleDbConnection(constr);
 
            con.Open();
 
            OleDbCommand commnd = new OleDbCommand();
            commnd.Connection = con;
            commnd.CommandType = CommandType.StoredProcedure;
            commnd.CommandText = "group=ADMIN;object=Procs;name=Addition";
 
            OleDbParameter paramA = new OleDbParameter();
            paramA.ParameterName = "A";
            paramA.OleDbType = OleDbType.Integer;
            paramA.Direction = ParameterDirection.Input;
            paramA.Value = Int32.Parse(var1.Text);
 
            OleDbParameter paramB = new OleDbParameter();
            paramB.ParameterName = "B";
            paramB.OleDbType = OleDbType.Integer;
            paramB.Direction = ParameterDirection.Input;
            paramB.Value = Int32.Parse(var2.Text);
 
            OleDbParameter paramReturnValue = new OleDbParameter();
            paramReturnValue.ParameterName = "C";
            paramReturnValue.OleDbType = OleDbType.Integer;
            paramReturnValue.Direction = ParameterDirection.ReturnValue;
 
            commnd.Parameters.Add(paramA);
            commnd.Parameters.Add(paramB);
            commnd.Parameters.Add(paramReturnValue);
 
            commnd.ExecuteNonQuery();
 
            int returnValue = (int)commnd.Parameters["C"].Value;
 
            Output.Items.Add(returnValue);
 
            con.Close();
 
        }
    }
}

[mldisibio]

I noticed in your first post, you added the return parameter to the parameter collection first, but you tagged it incorrectly as ParameterDirection.Output.

In the second post, you tagged it correctly as ParameterDirection.ReturnValue, but you add it to the collection last.

I believe MSDN states that ReturnValue parameters always need to be added to the ParameterCollection first, so try that again.

Also, not seeing your actual stored procedure, make sure it is indeed a ReturnValue and not an output paramater.

In SqlServer, for example, a ReturnValue is returned by the sql "RETURN" statement.
An output parameter is declared in the procedure definition, and the parameter is filled during the procedure. There may or may not also be a RETURN statement, but it is unrelated to the output parameter.

Also, SqlServer at least, has an implicit return value of 0 when successful, whether you declare it or not, so that may explain why you get a 0 in your text box.

[johndonnelly]

Hi and thank you for your response. You are right it was an Output Parameter. I still only get a 0 when I make that change though.

I'm not understanding your last paragraph about 0 being returned when successful.

I had a look around on the server and there is another object called AdditionParams where I found all the attribute of each parameter and there is a place for their value. It looks like the Addition proc might look to that object for the A and B values and return the C value there??

Knowing that, how would I approach this? Write to the AdditionParams object, run the proc with no added params and read the C value???

Thanks for your help.

[mldisibio]

Can you post the sql for both procedures?
Please enclose the procedures in CODE tags. Also, you can cut out any irrelevant statements if the procedures are long. Basically, we need to look at the procedure declarations (usually at the beginning), any calls to other procedures, and any statements that set the parameters.

Just for clarification, what database are you using?

What I mean by SQL Server returns an implicit zero is that if the procedure completes without error, and you do not have a RETURN statement, SQL Server implicitly returns a value of 0 to indicate success. So, even if you do not specify a RETURN statement in your sql procedure, if you create a Parameter with a ReturnValue direction in ADO.Net, it will be filled with a zero value.

The only reason I pointed that out is that if you mistakenly assign a ReturnValue parameter to your collection instead of an output parameter, and the value in your TextBox is always zero, it might be because it it simply reading the implicit return value of zero.

[johndonnelly]

I really appreciate your help.

I don't have access to the procedures unfortunately. I just have API documentation which is based on the old ADO. The procs are in ENGLISH a query language used on the PICK OS.

The database is on a PICK system with multivariant fields and subvalues etc which is why I have to use the ADP provider. ADP is a computer system for car dealerships and they are very protective of their database. I have access to a training database.

I work for a chain of dealerships and I have to get proficient in the API before they will allow us access to our own data. The ADP chief software engineer really doesn't want to work with ADO.Net. Everytime I ask him a question he sends VB6 code and says it should work.I suppose I could work in VB6. Apparently I am not converting correctly to C# and .Net.

Here's his latest:

"John,

If it returns zero, then it is not working correctly (unless you added 0 + 0).

You do not need to give it the group or object values.

I made a VB 6 version of the Addition tester in a bare bones code to make it easier to see (using the ADO Tester code as a guide) and tested it against the TRAIN36 product. This should help you determine where your coding issues are.

Here is my code – I highlighted the important sections of code. Yellow is supporting code and blue is the critical code in the API call itself."

Option Explicit
 
Dim PageConn As ADODB.Connection
Dim PageCmd As ADODB.Command
Dim StrConnData As String
Dim StrCommand As String
Dim sHost As String
Dim sProd As String
Dim sServer As String
Dim sPasswd As String
Dim iVarA As Integer
Dim iVarB As Integer
Dim iSum As Integer
 
Private Sub CmdClose_Click()
    Unload Me
End Sub
 
Private Sub cmdExecute_Click()
    Dim ErrMsg As String
    Dim ConnOpen As Boolean
    Dim CmdOpen As Boolean
    Dim ParamName As String
    Dim ParamValue As String
    Dim ParamDirection As String
    Dim ParamType As String
    Dim Param As ADODB.Parameter
    On Error GoTo ExitExecute
    '
    ErrMsg = ""
    ConnOpen = False
    CmdOpen = False
    '
    ' Check values have been entered
    '
    If txtHost.Text = "" Then Exit Sub
    If txtProd.Text = "" Then Exit Sub
    If txtServer.Text = "" Then Exit Sub
    If txtPasswd.Text = "" Then Exit Sub
    If txtVarA.Text = "" Then Exit Sub
    If txtVarB.Text = "" Then Exit Sub
    '
    ' Assign variables from the text boxes and check type
    '
    sHost = txtHost.Text
    sProd = txtProd.Text
    sServer = txtServer.Text
    sPasswd = txtPasswd.Text
    If IsNumeric(txtVarA.Text) Then
        iVarA = CInt(txtVarA.Text)
    Else
        MsgBox "Variable A is not numeric", vbCritical
        Exit Sub
    End If
    If IsNumeric(txtVarB.Text) Then
        iVarB = CInt(txtVarB.Text)
    Else
        MsgBox "Variable B is not numeric", vbCritical
        Exit Sub
    End If
    '
    ' Open connection to DMS
    '
    ErrMsg = "Connection to " & sHost & ", " & sProd & "/" & sServer & " failed."
    Set PageConn = CreateObject("ADODB.Connection")
    PageConn.Provider = "ADPProv.ADPProv.1"
    PageConn.CursorLocation = adUseClient
    PageConn.ConnectionTimeout = 0
    StrConnData = "host=" & sHost & "; product=" & sProd & "; server=" & sServer & "; productpassword=" & sPasswd & "; pooling=FALSE; port=10223"
    PageConn.Open StrConnData, "", ""
    ConnOpen = True
    '
    ' Execute Proc
    '
    ErrMsg = "Execute of Addition Proc failed."
    Set PageCmd = CreateObject("ADODB.Command")
    PageCmd.ActiveConnection = PageConn
    PageCmd.CommandTimeout = 480
    StrCommand = "proc=Addition"
    PageCmd.CommandText = StrCommand
    PageCmd.Parameters.Refresh
    '
    ' This for loop is for illustration only
    '
    For Each Param In PageCmd.Parameters
        Select Case Param.Direction
            Case 1
                ParamDirection = "In"
            Case 2
                ParamDirection = "Out"
            Case 3
                ParamDirection = "In/Out"
            Case Else
                ParamDirection = "Unknown"
        End Select
        '
        Select Case Param.Type
            Case adBSTR
                ParamType = "String"
            Case adDecimal
                ParamType = "Number"
            Case adDate
                ParamType = "Date"
            Case adDBTime
                ParamType = "Time"
            Case Else
                ParamType = Param.Type
        End Select
        Select Case Param.Name
            Case "A"
                If ParamType = "Number" And IsNumeric(iVarA) Then
                    PageCmd.Parameters(Param.Name).Value = iVarA
                End If
            Case "B"
                If ParamType = "Number" And IsNumeric(iVarB) Then
                    PageCmd.Parameters("B").Value = iVarB
                End If
        End Select
    Next
    '
    ' Ignore above For loop and assign the values to add together
    '
    PageCmd.Parameters("A").Value = iVarA
    PageCmd.Parameters("B").Value = iVarB
    PageCmd.Parameters("C").Value = 0
    PageCmd.Execute
    CmdOpen = True
    iSum = PageCmd.Parameters("C").Value
    txtSum.Text = CStr(iSum)
    '
    ' Wrap Up and exit
    '
    On Error GoTo 0
    DoEvents
    If CmdOpen Then
        Set PageCmd = Nothing
        CmdOpen = False
    End If
    If ConnOpen Then
        PageConn.Close
        Set PageConn = Nothing
        ConnOpen = False
    End If
    MsgBox "Done", vbInformation
    Exit Sub
    '
    ' Handle any errors
    '
ExitExecute:
    MsgBox ErrMsg & vbLf & Error, vbCritical
    On Error GoTo 0
    DoEvents
    If CmdOpen Then
        Set PageCmd = Nothing
        CmdOpen = False
    End If
    If ConnOpen Then
        PageConn.Close
        Set PageConn = Nothing
        ConnOpen = False
    End If
End Sub
 

Again thanks for your help.

[mldisibio]

I feel sorry for your situation, you are working against a black box.

Looking at his sample code, I would conclude he is calling "proc=Addition" directly, so I don't think you should change to the "AdditionParams" object.

From an ADO.Net perspective, your code looks like it should be correct. I do not see any "obvious" errors. Sometimes connections strings are different between legacy ADO and ADO.Net, but the connection would not be open if the connection string you are using is incorrect. And looking at his legacy connection code, I do not see any obvious reason why the ADO.Net should not work. At a minimum, it would throw some "Provider not found" error or such if there was an obvious showstopper.

- When you say you tried with "6" and "5", did you hard code those in? And did you try to display or view the result using the debugger to examime parameter "C" directly instead of relying on the form?

- I noticed his string uses "productpassword"; did you try keeping that instead of just "password"? Also, are you sure that by adding "group=ADMIN" you are addressing the correct stored procedure?

This is tough. I guess you can try using the debugger and making sure the connection is truly opened (although it would throw an exception if it wasn't) and then perhaps put a try/catch around the ExecuteNonQuery statement to make sure it is truly executing.

I am at a loss. I have never heard of this PICK database. One last try might be to use the System.Data.Odbc library instead of OleDb...but I'm just shooting in the dark.

Also...are there any tables you know about where you can test a very simple "Select" statement, just to confirm the database is capable of returning data?

[mldisibio]

mmm...I came across one (count 'em - one) post regarding this ADPProv Provider;
This might even be your post, as it is so similar. However, I see one difference:

I figured it out. See the underlined changes below. I should not have used TableDirect but Text and then any string is cool.

private void button1_Click(object sender, EventArgs e)
{
string constr = "provider=ADPProv.ADPProv.1;host=" + Host.Text;
constr = constr + ";product=" + Product.Text;
constr = constr + ";server=" + Server.Text;
constr = constr + ";password=" + Password.Text;
constr = constr + ";pooling=TRUE";
 
OleDbConnection con = new OleDbConnection(constr);
 
OleDbCommand command = new OleDbCommand();
command.CommandType = System.Data.CommandType.Text;
command.CommandText = "group=ADMIN;object=Object";
command.Connection = con;
con.Open();
 
OleDbDataReader reader = command.ExecuteReader();
 
int columnCount = reader.FieldCount;
while (reader.Read())
{
for (int i = 0; i < columnCount; i++)
{
Output.Items.Add(reader.GetName(i).ToString()+"= " + reader.GetValue(i).ToString());
}
}
 
reader.Close();
con.Close();
}

Did you try setting your CommandType to "Text" instead of "StoredProcedure"?
This PICK thingy may not have any concept of stored procedure.

[johndonnelly]

These are great comments. I will try each one over the weekend.

That was my post on experts-exchange I believe when I needed help getting the connection to work and I solved it myself. But this is kind of crazy. I may just skip this exercise and move on.

If I ever needed to create a stored proc and use it I think I could get it to work. Just working against an unknown is hard.

I really appreciate you talking this through with me. The rest of the net is not only silent on PICK but they don't respond much on non SQL ADO.Net

I'll post soon. Thanks again.

[johndonnelly]

I tried all your suggestions and none of them totally fixed the code. However I think I am now on the right track. Maybe you can confirm my thinking and the direction I think I need to pursue.

I ran a bunch of different commnd.CommandType.Text values and some gave me no error (but 0 still) and some gave me an error. I think "no error" is a dead end and I also think the IProc Interface error is the right direction. I believe this means that .Net is saying "Ok we are calling a Stored Procedure but I can't get the provider to hook me up."

As opposed to paramC is always zero because it is set to zero and never is acted on because .Net sees no procedure request????

Here's my Error list:

These did not give errors:
commnd.CommandText = "group=ADMIN;object=AdditionParams;name=Additi on";
commnd.CommandText = "group=ADMIN;object=Procs;name=Addition";
commnd.CommandText = "group=ADMIN;object=Procs;methodname=Addition" ;

These did give me errors:
commnd.CommandText = "group=ADMIN;MethodName=Addition"; X2Provider Error <Object not found>
commnd.CommandText = "group=ADMIN;object=Procs;proc=Addition"; X2Provider Error<Internal Error:Failed to get the IProc Interface>
commnd.CommandText = "proc=Addition"; X2Provider Error <Internal Error:Failed to get the IProc Interface>
commnd.CommandText = "group=ADMIN;object=ProcParams;name=Addition"; Could not find object <ProcParams>
X2Provider Error <Object not found>
commnd.CommandText = "group=ADMIN;object=AdditionParams"; Could not find object <AdditionParams ?, ?, ?> X2Provider Error <Object not found>
commnd.CommandText = "group=ADMIN;name=Addition"; Could not find object <> X2Provider Error <Object not found>
commnd.CommandText = "group=ADMIN;proc=Addition"; X2Provider Error <Internal Error:Failed to get the IProc Interface>

Do you have any idea what I could do to get "proc=Addition" to take?

Thanks so much!

John

[mldisibio]

I am trying to be helpful, but I don't want to waste your time either, as I really don't see any obvious solution.
Honestly, if certain calls are giving you errors, then my conclusion is that the calls which do not give errors are syntactically correct. You are connecting, so that is not the issue, and when the syntax is incorrect, you get an exception, including "object not found" errors.

Just to be clear on all the tests:
- Set your Command object to CommandType.StoredProcedure and try the "commnd.CommandText = "group=ADMIN;object=Procs;name=Addition";"
- Set your Command object to CommandType.Text and try "commnd.CommandText = "group=ADMIN;object=Object;proc=Addition";"

One last suggestion: can you add a C# version of his "Illustration purposes loop". He calls cmd.Parameters.Refresh, which queries the database for the parameter types and names. You can then print the names and types to the Console or such. You would do this without adding the parameters yourself. It is a debugging procedure. Make sure they are the types you are expecting and the names you are using!

If all else fails, even if you don't have access to VB6, I believe you could write a classic ASP web page and make use of the old ADO libraries, to see if in fact you get a return value from your test environment using the old code. It would look very similar to his VB6 code.

[johndonnelly]

This is not a waste of time for me. I am learning a ton about C# and ADO.Net

However I don't want to waste your time.

I did some foreach loops to gather parameter properties and during debugging the collection had no members so I'm not reaching the proc id on't believe.

I tried all execute methods ExecuteNonQuery, ExecuteScalar and ExecuteDataReader and eliminated the possiblity of the Execute method being the culprit in the failure to get IProc Interface.

I think I need to move on so don't bother responding unless you just have to tell me a new idea!

Thanks for all your help.

[mldisibio]

Well, kudos to you for sticking in there and really trying. I feel frustrated too,that you couldn't solve it. But maybe if you drop it for a few weeks you may come across something else that sheds some light on what is missing here.

The cool part is that when anyone in the entire world does a Google on "ADPProv.ADPProv.1", they will find your post here. You're famous!

In any case, I hope eventually you get the breakthrough you need so that you can work with the language and ADO libraries of your choice.

[johndonnelly]

Just wanted to post this because I gave up on C# and ADO.Net with this provider so I went at getting VS2008 to compile the VB6 code listed above.

I attached a screenshot of the references I had to add and the namespace I imported to make the project work. I also had to delete some error handling code with DoEvents() etc

I really wanted to use C# ADO.Net but I don't think the provider can handle it.

Oh well at least I got it to work!

Here's the code I ended up with:

Option Explicit On
 
Imports Microsoft.VisualBasic
 
Public Class Form1
 
    Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
        Dim PageConn As ADODB.Connection
        Dim PageCmd As ADODB.Command
        Dim StrConnData As String
        Dim StrCommand As String
        Dim sHost As String
        Dim sProd As String
        Dim sServer As String
        Dim sPasswd As String
        Dim iVarA As Integer
        Dim iVarB As Integer
        Dim iSum As Integer
        Dim ErrMsg As String
        Dim ConnOpen As Boolean
        Dim CmdOpen As Boolean
        Dim ParamName As String
        Dim ParamValue As String
        Dim ParamDirection As String
        Dim ParamType As String
        Dim Param As ADODB.Parameter
 
        ' Check values have been entered
 
        If txtHost.Text = "" Then Exit Sub
        If txtProd.Text = "" Then Exit Sub
        If txtServer.Text = "" Then Exit Sub
        If txtPasswd.Text = "" Then Exit Sub
        If txtVarA.Text = "" Then Exit Sub
        If txtVarB.Text = "" Then Exit Sub
        '
        ' Assign variables from the text boxes and check type
        '
        sHost = txtHost.Text
        sProd = txtProd.Text
        sServer = txtServer.Text
        sPasswd = txtPasswd.Text
        If IsNumeric(txtVarA.Text) Then
            iVarA = CInt(txtVarA.Text)
        Else
            MsgBox("Variable A is not numeric", vbCritical)
            Exit Sub
        End If
        If IsNumeric(txtVarB.Text) Then
            iVarB = CInt(txtVarB.Text)
        Else
            MsgBox("Variable B is not numeric", vbCritical)
            Exit Sub
        End If
        '
        ' Open connection to DMS
        '
        ErrMsg = "Connection to " & sHost & ", " & sProd & "/" & sServer & " failed."
        PageConn = CreateObject("ADODB.Connection")
        PageConn.Provider = "ADPProv.ADPProv.1"
        PageConn.CursorLocation = ADODB.CursorLocationEnum.adUseClient
        PageConn.ConnectionTimeout = 0
        StrConnData = "host=" & sHost & "; product=" & sProd & "; server=" & sServer & "; productpassword=" & sPasswd & "; pooling=FALSE; port=10223"
        PageConn.Open(StrConnData, "", "")
        ConnOpen = True
        '
        ' Execute Proc
        '
        ErrMsg = "Execute of Addition Proc failed."
        PageCmd = CreateObject("ADODB.Command")
        PageCmd.ActiveConnection = PageConn
        PageCmd.CommandTimeout = 480
        StrCommand = "proc=Addition"
        PageCmd.CommandText = StrCommand
        PageCmd.Parameters.Refresh()
        '
        ' This for loop is for illustration only
        '
        For Each Param In PageCmd.Parameters
            Select Case Param.Direction
                Case 1
                    ParamDirection = "In"
                Case 2
                    ParamDirection = "Out"
                Case 3
                    ParamDirection = "In/Out"
                Case Else
                    ParamDirection = "Unknown"
            End Select
            '
            Select Case Param.Type
                Case ADODB.DataTypeEnum.adBSTR
                    ParamType = "String"
                Case ADODB.DataTypeEnum.adDecimal
                    ParamType = "Number"
                Case ADODB.DataTypeEnum.adDate
                    ParamType = "Date"
                Case ADODB.DataTypeEnum.adDBTime
                    ParamType = "Time"
                Case Else
                    ParamType = Param.Type
            End Select
            Select Case Param.Name
                Case "A"
                    If ParamType = "Number" And IsNumeric(iVarA) Then
                        PageCmd.Parameters(Param.Name).Value = iVarA
                    End If
                Case "B"
                    If ParamType = "Number" And IsNumeric(iVarB) Then
                        PageCmd.Parameters("B").Value = iVarB
                    End If
            End Select
        Next
        '
        ' Ignore above For loop and assign the values to add together
        '
        PageCmd.Parameters("A").Value = iVarA
        PageCmd.Parameters("B").Value = iVarB
        PageCmd.Parameters("C").Value = 0
        PageCmd.Execute()
        CmdOpen = True
        iSum = PageCmd.Parameters("C").Value
        txtSum.Text = CStr(iSum)
        '
        ' Wrap Up and exit
        '
        PageConn.Close()
    End Sub
 
    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
 
        txtHost.Text = "207.109.69.61"
        txtProd.Text = "TRAIN36"
        txtServer.Text = "TEST1"
        txtPasswd.Text = "TRAIN361"
        txtVarA.Text = ""
        txtVarB.Text = ""
        txtSum.Text = ""
 
    End Sub
 
    Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
        End
    End Sub
 
End Class

[johndonnelly]

I couldn't attach a jpg file. It kept telling me it was too big even at 8 kb!?!

I imported the namespace Microsoft.VisualBasic as you can see in the code.

I added these references in addition to the usual System ones used in Windows forms development including System.Data.

Reference Name Type Version
adodb .Net 7.0.3300.0
dao .Net 10.0.4504.0
Microsoft.VisualBasic.Compatibility .Net 8.0.0.0
Microsoft.VisualBasic.Compatibility.Data .Net 8.0.0.0

Thanks for all the help,

JD