Introduction

This is the fifth article discussing connectivity scenarios involving IBM® DB2® Universal Database^™ (UDB) for Linux, UNIX® and Windows® Version 8, DB2 UDB for iSeries 5.2 and DB2 UDB for z/OS V8*. As in the third and fourth parts of this article series, the latest versions are being used; however, the instructions shown may apply to other versions.

The focus of this article is on workstation application development connectivity. This means we will provide sample programs developed on workstation platforms (Windows) using ADO and ADO.NET, where each program connects to a DB2 UDB database (any platform), selects from a table, and disconnects. The sample programs have been tested on a Microsoft® Windows 2000 platform. Due to space limitations, the listings in this article contain only code snippets. However, we provide at the end of this article the source code of the complete functional sample programs in a zip file. We also provide step-by-step guides on how to create the sample programs using Microsoft Visual Studio 6 and Microsoft Visual Studio .NET.

Due to space constraints in this article, we also are not showing the output of the sample programs; however, the file ADO_ADONET_Results.zip contains the print screens of the tests that were performed using all of the sample programs against a DB2 UDB for Linux, UNIX and Windows, DB2 UDB for zSeries, and DB2 UDB for iSeries server.

Working as a consultant, I have encountered situations where a sample program would have been handy to test if the application connectivity setup was correct. The sample programs in this article can be used for this purpose. With DB2 UDB for Linux, UNIX and Windows V8 you can now test several types of connections using the Configuration Assistant (CA); however, the sample programs will be handy for previous version of DB2 UDB and also they give you more detail on the connectivity setup.

This article should be useful also to database administrators (DBAs) who normally don't need to code programs. Having a basic understanding about how to write a program against a DB2 database should be advantageous to them when interacting with their application developers.

The programs in this article have been based on the sample programs supplied with the DB2 UDB Application Development client (under directory sqllib/samples); however, they have been simplified for ease of understanding.

This article describes the following connectivity scenarios:

• ADO:
• Scenario 1: Connecting to a DB2 UDB database using the IBM OLE DB provider for DB2 (IBMDADB2)
• Scenario 2: Connecting to a DB2 UDB database using the Microsoft OLE DB Provider for ODBC (MSDASQL)
• ADO.NET:
• Scenario 3: Connecting to a DB2 UDB database using the IBM DB2 .NET Data Provider
• Scenario 4: Connecting to a DB2 UDB database using the Microsoft OLE DB .NET Data Provider
• Scenario 5: Connecting to a DB2 UDB database using the Microsoft ODBC .NET Data Provider

Back to top

Scenario 1 - Connecting to a DB2 UDB database using the IBM OLE DB provider for DB2 (IBMDADB2)

Listing 1 and Listing 2 show how to connect to a DB2 database using the MS OLE DB Provider for ODBC and issue a simple select statement. You can find the sample applications dbConn_vb_ado_ibmdadb2.bas and dbConn_vc_ado_ibmdadb2.cpp in the source code zip file here.

Dim cmd As ADODB.Command
Dim con As ADODB.Connection
Dim rst As ADODB.Recordset

Set con = New ADODB.Connection
con.ConnectionString = "DSN=SAMPLE;UID=db2admin;PWD=mypsw;"
con.Provider = "IBMDADB2"
con.CursorLocation = adUseClient
con.Open

Set cmd = New ADODB.Command
Set cmd.ActiveConnection = con
cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1"
Set rst = cmd.Execute()
MsgBox "Successful retrieval of record. Column" + _
           " 'IBMREQD' has a value of '" + _
           rst.Fields.Item("IBMREQD").Value + "'" + vbCrLf

rst.Close
con.Close

#import "C:\program files\common files\system\ado\msado15.dll" \
	no_namespace rename( "EOF", "adoEOF")
[...]
_CommandPtr pCmd  = NULL;			
_ConnectionPtr pConnection = NULL;	
_RecordsetPtr  pRst = NULL;
_bstr_t strMsg;
HRESULT  hr;
try {
    hr = pConnection.CreateInstance(__uuidof(Connection));
    if FAILED(hr) { _com_issue_error(hr);}
    pConnection->ConnectionString =     
                         _bstr_t("DSN=sample;UID=db2admin;PWD=mypsw;");
    pConnection->CursorLocation = adUseClient;
    pConnection->Provider = "IBMDADB2";
    pConnection->Open("","","",adConnectUnspecified);
    
    hr = pCmd.CreateInstance(__uuidof(Command));
    if FAILED(hr){_com_issue_error(hr);}
    pCmd->ActiveConnection = pConnection;
    pCmd->CommandText = _bstr_t("SELECT * FROM SYSIBM.SYSDUMMY1");       
    pRst = pCmd->Execute(NULL,NULL,adOptionUnspecified); 
    strMsg  = _bstr_t("  Successful retrieval of record.");
    strMsg += _bstr_t(" Column 'IBMREQD' has a value of '");
    strMsg += _bstr_t(pRst->Fields->Item["IBMREQD"]->Value) ;
    strMsg += _bstr_t("'");
    printf("%s\n",(LPCSTR)strMsg);

    pRst->Close();
    pConnection->Close();
} catch(_com_error &e) { [...] }

Back to top

Scenario 2 - Connecting to a DB2 UDB database using the Microsoft OLE DB Provider for ODBC (MSDASQL)

Listing 3 and Listing 4 show how to connect to a DB2 database using the MS OLE DB Provider for ODBC and issue a simple select statement. You can find the sample applications dbConn_vb_ado_msdasql.bas and dbConn_vc_ado_msdasql.cpp in the source code zip file here.

Dim cmd As ADODB.Command
Dim con As ADODB.Connection
Dim rst As ADODB.Recordset

Set con = New ADODB.Connection
con.ConnectionString = "DSN=SAMPLE;UID=db2admin;" + _
                 "PWD=mypsw;Driver={IBM DB2 ODBC DRIVER};"
con.Provider = "MSDASQL"
con.CursorLocation = adUseClient
con.Open

Set cmd = New ADODB.Command
Set cmd.ActiveConnection = con
cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1"
Set rst = cmd.Execute()
MsgBox "Successful retrieval of record. Column" + _
         " 'IBMREQD' has a value of '" + _
          rst.Fields.Item("IBMREQD").Value + _
          "'" + vbCrLf
          
rst.Close
con.Close

#import "C:\program files\common files\system\ado\msado15.dll" \
	no_namespace rename( "EOF", "adoEOF")
[...]
_CommandPtr pCmd  = NULL;			
_ConnectionPtr pConnection = NULL;		
_RecordsetPtr  pRst = NULL;
_bstr_t strMsg;			
HRESULT  hr;	
try{
    hr = pConnection.CreateInstance(__uuidof(Connection));
    if FAILED(hr){_com_issue_error(hr);}
    pConnection->ConnectionString= _bstr_t("DSN=sample;
    		UID=db2admin;PWD=mypsw;Driver={IBM DB2 ODBC DRIVER};");
    pConnection->CursorLocation = adUseClient;
    pConnection->Provider = "MSDASQL";
    pConnection->Open("","","",adConnectUnspecified);
    
    hr = pCmd.CreateInstance(__uuidof(Command));
    if FAILED(hr) {_com_issue_error(hr);}
    pCmd->ActiveConnection = pConnection;
    pCmd->CommandText = _bstr_t("SELECT * FROM SYSIBM.SYSDUMMY1");
    pRst = pCmd->Execute(NULL,NULL,adOptionUnspecified); 
    strMsg  = _bstr_t("  Successful retrieval of record.");
    strMsg += _bstr_t(" Column 'IBMREQD' has a value of '");
    strMsg += _bstr_t(pRst->Fields->Item["IBMREQD"]->Value) ;
    strMsg += _bstr_t("'");
    printf("%s\n",(LPCSTR)strMsg);

    pRst->Close();
    pConnection->Close();
} catch(_com_error &e){ [...] }

¹You can also specify the provider in the Connection String property (i.e. Provider=IBMDADB2;). However, you should only specify either the Provider property or the provider argument in the Connection String property.

As shown in Table 4, the CursorLocation property of a Connection object constraints the values of the CursorType and LockType properties of the Recordset objects that are associated with it.

²The LockType property is not supported by the IBM OLE DB provider for DB2.

Back to top

Scenario 3 - Connecting to a DB2 UDB database using the IBM DB2 .NET Data Provider

Listing 5 and Listing 6 show how to connect to a DB2 database using the IBM DB2 .NET Data Provider and issue a simple select statement. You can find the sample applications dbConn_vb_adoNET_ibmdatadb2.vb and dbConn_cs_adoNET_ibmdatadb2.cs in the source code zip file here.

Imports IBM.Data.DB2
[...]
Dim cmd As DB2Command
Dim con As DB2Connection
Dim rdr As DB2DataReader
Dim v_IBMREQD As String
Try
    con = New DB2Connection("Database=SAMPLE;" +
                            "UID=db2admin;PWD=mypsw;")
    cmd = New DB2Command()
    cmd.Connection = con
    cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1"
    cmd.CommandTimeout = 20
    con.Open()

    rdr = cmd.ExecuteReader(CommandBehavior.SingleResult)
    v_IBMREQD = "";
    while (rdr.Read() == true) {
        v_IBMREQD = rdr.GetString(0); }
    strMsg = "  Successful retrieval of record. Column " +
		  "'IBMREQD' has a value of '" +
		  v_IBMREQD + "'";
    Console.WriteLine(strMsg);
    
    rdr.Close()
    con.Close()
Catch myException As DB2Exception
	[...]
End Try

using IBM.Data.DB2;
[...]
DB2Command cmd = null;
DB2Connection con = null;
DB2DataReader rdr = null;
int rowCount;
try{
     con = new DB2Connection("Database=SAMPLE;UID=db2admin;PWD=mypsw;");
     cmd = new DB2Command();
     cmd.Connection = con;
     cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1";
     cmd.CommandTimeout = 20;
     con.Open();
     	
     rdr = cmd.ExecuteReader(CommandBehavior.SingleResult);
     v_IBMREQD = "";
     while (rdr.Read() == true) {
      v_IBMREQD = rdr.GetString(0); }
     strMsg = "  Successful retrieval of record. Column" +
     	    " 'IBMREQD' has a value of '" + v_IBMREQD + "'";
     Console.WriteLine(strMsg);
     
     rdr.Close();
     con.Close();
} catch (DB2Exception myException) { [...] }

Back to top

Scenario 4 - Connecting to a DB2 UDB database using the Microsoft OLE DB .NET Data Provider

Listing 7 and Listing 8 show how to connect to a DB2 database using the MS OLE DB .NET Data Provider and issue a simple select statement. You can find the sample applications dbConn_vb_adoNET_msoleddbnet.vb and dbConn_cs_adoNET_msoleddbnet.cs in the source code zip file here.

Imports System.Data.OleDb
[...]
Dim cmd As OleDbCommand
Dim con As OleDbConnection
Dim rdr As OleDbDataReader
Dim v_IBMREQD As String
Try
    con = New OleDbConnection("DSN=SAMPLE;UID=db2admin;PWD=mypsw;" + _
                                      "Provider='IBMDADB2';")
    cmd = New OleDbCommand()
    cmd.Connection = con
    cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1"
    cmd.CommandTimeout = 20
    con.Open()

    rdr = cmd.ExecuteReader(CommandBehavior.SingleResult)
    While rdr.Read()
        v_IBMREQD = rdr.GetString(0)
    End While
    Console.WriteLine('IBMREQD' has a value of '" + v_IBMREQD + "'")

    rdr.Close()
    con.Close()
Catch myException As OleDbException
	[...]
End Try

using System.Data.OleDb;
[...]
OleDbCommand cmd = null;
OleDbConnection con = null;
OleDbDataReader rdr = null;
int rowCount;
try
{
   con = new OleDbConnection("DSN=SAMPLE;UID=db2admin;PWD=mypsw;" + 
                                            "Provider='IBMDADB2';");
   cmd = new OleDbCommand();
   cmd.Connection = con;
   cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1";
   cmd.CommandTimeout = 20;
   con.Open();
   
   rdr = cmd.ExecuteReader(CommandBehavior.SingleResult);
   v_IBMREQD = "";
   while (rdr.Read() == true) {
         v_IBMREQD = rdr.GetString(0); }
   strMsg = "  Successful retrieval of record. Column" +
		    " 'IBMREQD' has a value of '" + v_IBMREQD + "'";
   Console.WriteLine(strMsg);

   rdr.Close();
   con.Close();
} catch (OleDbException myException) { [...] }

Back to top

Scenario 5 - Connecting to a DB2 UDB database using the Microsoft ODBC .NET Data Provider

Listing 9 and Listing 10 show how to connect to a DB2 database using the MS ODBC .NET Data Provider and issue a simple select statement. You can find the sample applications dbConn_vb_ado_msodbcnet.vb and dbConn_cs_ado_msodbcnet.cs in the source code zip file here.

Imports Microsoft.Data.Odbc
[...]
Dim cmd As OdbcCommand
Dim con As OdbcConnection
Dim rdr As OdbcDataReader
Dim v_IBMREQD As String
Try
    con = New OdbcConnection("DSN=SAMPLE;UID=db2admin;PWD=mypsw;" + _
                                   "Driver={IBM DB2 ODBC DRIVER};")
    cmd = New OdbcCommand()
    cmd.Connection = con
    cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1"
    cmd.CommandTimeout = 20
    con.Open()

    rdr = cmd.ExecuteReader(CommandBehavior.SingleResult)
    While rdr.Read()
        v_IBMREQD = rdr.GetString(0)
    End While
    Console.WriteLine('IBMREQD' has a value of '" + v_IBMREQD + "'")
    rdr.Close()
    con.Close()
Catch myException As OdbcException
	[...]
End Try

using Microsoft.Data.Odbc;
[...]
OdbcCommand cmd = null;
OdbcConnection con = null;
OdbcDataReader rdr = null;
int rowCount;
try
{
   con = new OdbcConnection("DSN=SAMPLE;UID=;PWD=;" + 
                                   "Driver={IBM DB2 ODBC DRIVER};");
   cmd = new OdbcCommand();
   cmd.Connection = con;
   cmd.CommandText = "SELECT * FROM SYSIBM.SYSDUMMY1";
   cmd.CommandTimeout = 20;
   con.Open();
   	
   rdr = cmd.ExecuteReader(CommandBehavior.SingleResult);
   while (rdr.Read() == true) {
         v_IBMREQD = rdr.GetString(0); }
   strMsg = "  Successful retrieval of record. Column" +
		    " 'IBMREQD' has a value of '" + v_IBMREQD + "'";
   Console.WriteLine(strMsg);
      
   rdr.Close();
   con.Close();
} catch (OdbcException myException) { [...] }

³MS ODBC .NET Data Provider is not part of the .NET Framework v1.0 and is available for download from Microsoft .NET Framework Download website.

³MS ODBC .NET Data Provider is not part of the .NET Framework v1.0 and is available for download from Microsoft .NET Framework Download website.

⁴Use the Database keyword only when using the IBM DB2 .NET Data Provider, otherwise use the DSN keyword.

Back to top

Registering the IBM DB2 Development Add-Ins for Visual Studio .NET

If Visual Studio .NET was installed prior to installing the DB2 UDB V8 Application Development Client (or higher), the IBM DB2 Development Add-Ins for Visual Studio .NET is automatically registered during the installation of DB2.

Back to top

Step-by-step guide 1: Creating a Visual Basic ADO Application

The following steps create a Visual Basic ADO application using MS Visual Basic 6.

1. Create a Visual Basic project
   1. On the File menu, select New Project
   2. On the New Project dialog, select Standard EXE project template. The new Visual Basic project will consist of one form (Form1) and the Project Explorer window should look similar to Figure 6.
   
   Figure 6 - Creating a new Visual Basic project
   
   
2. Copy and paste the Visual Basic sample application:
   1. On the Project menu, select Add Module.
   2. On the Add Module dialog, toggle the New tab and select Module. The Project Explorer window should show the new module (Module1) and should look similar to Figure 7.
   3. On the Project Explorer window, Right-Click on Form1 and select Remove Form1. Typically, you would use a form to provide a GUI to the user. For our sample applications, a pop-up message box will suffice.
   4. Copy and paste one of the Visual Basic ADO sample application (e.g., dbConn_vb_ado_ibmdadb2.bas) into Module1.
   
   Figure 7 - Adding the Visual Basic ADO sample application to the project
   
   
3. Rename the project and set the project Startup Object:
   1. On the Project Explorer window, Right-click on Project1 and select Project1 Properties
   2. On the Project Properties dialog, under Startup Object select Sub Main and under Project Name specify a new project name, e.g. dbConn_vb_ado_ibmdadb2.
   
   Figure 8 - Setting the Startup Object of the project
   
   
4. Add reference to MS ADO type library:
   1. On the Project menu, select References
   2. On the References dialog, scroll-down and place select Microsoft ActiveX Data Objects X.X Library. The X.X stand for the version of Microsoft Data Access Components (MDAC) installed on your system. On our system as shown on Figure 9, we had installed MDAC 2.8 and chose Microsoft ActiveX Data Objects 2.8 Library. If the type library is not listed, click Browse and select the type library from the directory it was installed in. For example, on our system msado15.dll located at C:\Program Files\Common Files\System\ADO
   
   Figure 9 - Adding reference to the MS ADO type library
   
   
5. Create an executable from within the Visual Basic IDE:
   1. On the File menu, select Save Project. Specify the project directory and name for the module Module1 (e.g. dbConn_vb_ado_ibmdadb2.bas)
   2. On the File menu, select Make <projectname>.exe. This will generate an executable in the directory that you specified.
   
   Figure 10 - Creating an executable program for the project
   
   
6. Create an executable from the command line.

   You can also create, from the command line, an executable for a Visual Basic project. At the command prompt, type:

   vb6 /m <projectname>.vbp

   e.g. vb6 /m dbConn_vb_ibmdadb2.vbp

   
   Figure 11 - Building the project from the command line
   
   

Back to top

Step-by-step guide 2: Creating a Visual C++ ADO application

The following steps create a Visual C++ ADO application using MS Visual C++ 6.

1. Create a Visual C++ project:
   1. On the File menu, select New
   2. On the New dialog, toggle the Projects tab and select Win32 Console Application project template. Specify the project name and directory under Project Name and Location respectively.
   3. On the Win32 Console Application dialog, select A simple application as the project template and click on the Finish button. The new VC++ project will consist of two C++ source files and one header file. The Project Workspace window should look similar to Figure 12.
   
   Figure 12 - Creating a new Visual C++ project
   
   
2. Copy and paste the VC++ sample application:
   1. Copy and paste one of the VC++ ADO sample applications (e.g. dbConn_vc_ado_ibmdadb2) into <projectname>.cpp file, as shown in Figure 13. Do not paste the into the precompiled header files: StdAfx.cpp, StdAfx.h.
   2. Copy and paste the ADO library headers declaration from the same sample application into the precompiled header file StdAfx.h, as shown in Figure 14.
   
   Figure 13 - Adding the Visual C++ ADO sample application to the project
   
   
   Figure 14 - Adding the sample application's ADO library headers to the precompiled header file
   
   
3. Create an executable from within the MS Visual C++ IDE:
   1. On the File menu, select Save All.
   2. On the Build menu, select Build <projectname>.exe. This will generate an executable file in the subdirectory Debug or Release under the project directory.
   
   Figure 15 - Creating an executable program for the project
   
   
4. Create an executable from the command line.

   You can also create, from the command line, an executable for a VC++ project. At the command prompt, type

   msdev <projectname>.dsp /make "<projectname> - Win32 Release" /rebuild

   e.g. msdev dbConn_vc_ado_ibmdadb2.dsp /make "dbConn_vc_ado_ibmdadb2 - Win32 Release" /rebuild

   
   Figure 16 - Building the project from the command line
   
   

Back to top

Step-by-step guide 3: Creating a Visual Basic ADO.NET application

The following steps create a Visual Basic ADO.NET application using MS Visual Studio .NET.

1. Create a Visual Basic .NET project:
   1. On the File menu, select New, then select Project
   2. On the New Project dialog, for Project Types select the Visual Basic Projects folder. For Templates, select Console Application project template. Specify the project name and directory under Name and Location respectively. The new VB .NET project will consist of two VB files (AssemblyInfo.vb and Module1.vb) and the Solution Explorer window should look similar to Figure 17.
   
   Figure 17 - Creating a new Visual Basic .NET project
   
   
2. Copy and paste the VB .NET sample application.

   Copy and paste one of the VB ADO.NET sample applications (e.g. dbConn_vb_adoNET_ibmdatadb2.vb) into Module1.vb.

   
   Figure 18 - Adding the Visual Basic ADO.NET sample application to the project
   
   
3. Add references for the type libraries used in the sample application:
   1. On the Project menu, select Add Reference
   2. On the Add Reference dialog, toggle the .NET tab, scroll-down and select the IBM.Data.DB2.dll and Microsoft Visual Basic .NET Runtime components, and click on Select. Both components should now be listed under Selected Components. Click OK. If the component is not listed, click Browse and select the component from the directory it was installed in. For example, on our system
   • IBM.Data.DB2.dll located at F:\Program Files\IBM\SQLLIB\BIN\netf10
   • Microsoft.Data.Odbc.dll located at C:\Program Files\Microsoft.NET\Odbc.Net
   3. In the Solution Explorer window, Right-click on the Module1.vb file and select Rename. Specify a new file name (e.g. dbConn_vb_adoNET_ibmdatadb2.vb). The Solution Explorer window should look similar to Figure 19
   
   Figure 19 - Adding references to the type libraries
   
   
4. Set the project Startup object:
   1. In the Solution Explorer window, Right-click on the project (e.g. dbConn_vb_adoNET_ibmdadb2) and select Properties.
   2. On the Property Pages dialog, under the Common Properties folder and the General tab, select Sub Main as the Startup Object.
   
   Figure 20 - Setting the Startup Object of the project
   
   
5. Build the solution from within the MS Visual Studio .NET IDE:
   1. On the File menu, select Save All.
   2. On the Build menu, select Build Solution. This will generate an executable in the subdirectory bin under the project directory.
   
   Figure 21 - Creating an executable program for the project
   
   
6. Create an executable from the command line.

   You can also create, from the command line, an executable for a Visual Basic .NET project. At the command prompt, type

   devenv /rebuild debug "<projectname>.sln"

   e.g. devenv /rebuild debug "dbConn_vb_adoNET_ibmdatadb2.sln"

   
   Figure 22 - Building the project from the command line
   
   
7. Compile the Visual Basic .NET file from the command line.

   Instead of generating the executable from a Visual Basic .NET project, you can also create an executable for a Visual Basic .NET file from the command line. At the command prompt, type the following:

   set tmpLibpath="F:\Program Files\IBM\SQLLIB\BIN\netf10" set tmpReference=IBM.Data.DB2.dll,Microsoft.VisualBasic.dll,System.dll,System.Data.dll vbc /libpath:%tmpLibpath% /reference:%tmpReference% /target:exe <filename>.vb /main:ConnectDb

   
   

   For example:

   set tmpLibpath="F:\Program Files\IBM\SQLLIB\BIN\netf10" set tmpReference=IBM.Data.DB2.dll,Microsoft.VisualBasic.dll,System.dll,System.Data.dll vbc /libpath:%tmpLibpath% /reference:%tmpReference% /target:exe dbConn_vb_adoNET_ibmdatadb2.vb /main:ConnectDb

   
   
   
   Figure 23 - Compiling the Visual Basic .NET file from the command line
   
   

Back to top

Step-by-step guide 4: Creating a Visual C# ADO.NET application

The following steps create a Visual C# ADO.NET application using MS Studio .NET.

1. Create a Visual Basic .NET project:
   1. On the File menu, select New, then select Project
   2. On the New Project dialog, for Project Types select the Visual C# Projects folder. For Templates, select Console Application project template. Specify the project name and directory under Name and Location respectively. The Solution Explorer window should look similar to Figure 24.
   
   Figure 24 - Creating a new Visual C# .NET project
   
   
2. Copy and paste the VC# .NET sample application.

   Copy and paste one of the VC# ADO.NET sample applications (e.g. dbConn_cs_adoNET_ibmdatadb2.cs) into Class1.cs file.

   
   Figure 25 - Adding the Visual C# ADO.NET sample application to the project
   
   
3. Add references for the type libraries used in the sample application:
   1. In the Solution Explorer window, Right-click on the project (e.g. dbConn_cs_adoNET_ibmdadb2) and select Add Reference
   2. On the Add Reference dialog, toggle the .NET tab, scroll-down and select the IBM.Data.DB2.dll component and click on Select. Both components should now be listed under Selected Components. Click OK. If the component is not listed, click Browse and select the component from the directory it was installed in. For example, on our system
   • IBM.Data.DB2.dll located at F:\Program Files\IBM\SQLLIB\BIN\netf10
   • Microsoft.Data.Odbc.dll located at C:\Program Files\Microsoft.NET\Odbc.Net
   3. In the Solution Explorer window, Right-click on the Class1.cs file and select Rename. Specify a new file name (e.g. dbConn_cs_adoNET_ibmdatadb2.cs). The Solution Explorer window should look similar to Figure 26
   
   Figure 26 - Adding references to the type libraries
   
   
4. Set the project Startup object:
   1. In the Solution Explorer window, Right-click on the project (e.g. dbConn_cs_adoNET_ibmdadb2) and select Properties.
   2. On the Property Pages dialog, under the Common Properties folder and the General tab, select Sub Main as the Startup Object.
   
   Figure 27 - Setting the Startup Object of the project
   
   
5. Build the solution from within the MS Visual Studio .NET IDE:
   1. On the File menu, select Save All.
   2. On the Build menu, select Build Solution. This will generate an executable in the subdirectory bin\Debug or bin\Release under the project directory.
   
   Figure 28 - Creating an executable program for the project
   
   
6. Create an executable from the command line.

   You can also create, from the command line, an executable for a Visual Basic .NET project. At the command prompt, type

   devenv /rebuild debug "<projectname>.sln"

   e.g. devenv /rebuild debug "dbConn_cs_adoNET_ibmdatadb2.sln"

   
   Figure 29 - Building the project from the command line
   
   
7. Compile the Visual C# .NET file from the command line.

   Instead of generating the executable from a Visual C# .NET project, you can also create an executable for a Visual C# .NET file from the command line. At the command prompt, type

   set tmpReference="F:\Program Files\IBM\SQLLIB\BIN\netf10\IBM.Data.DB2.dll";System.dll;System.Data.dll csc /reference:%tmpReference% /target:exe <filename>.cs /main:ConnectDb

   e.g. set tmpReference="F:\Program Files\IBM\SQLLIB\BIN\netf10\IBM.Data.DB2.dll";System.dll;System.Data.dll csc /reference:%tmpReference% /target:exe dbConn_cs_adoNET_ibmdatadb2.cs /main:ConnectDb

   
   Figure 30 - Compiling the Visual C# .NET file from the command line
   
   

Back to top

Downloads

Name	Size	Download method
Connectivity_ADO_ADONET.zip	25.2 KB
ADO_ADONET_Results.pdf	172.0 KB
SampleCode.zip	25 KB	FTP | HTTP
ADO_ADONET_Results.zip	315 KB

Information about download methods          Get Adobe® Reader®

Resources

• "Developing an Application Using Web Service Functions, DB2, and Visual Studio .Net".
  
  
• "Developing DB2 Schema using the IBM Explorer in VS.NET".
  
  
• "Developing an Application Using Web Service Functions, DB2, and Visual Studio .Net".
  
  
• Download DB2 FixPaks and clients used in this article.
  
  
• Download Microsoft Data Access Components (MDAC) used in this article.
  
  
• Download the MS ODBC .NET Data Provider used in this article.
  
  

About the authors

Comments

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Introduction
• IBM OLE DB provider for DB2 (IBMDADB2)
• Microsoft OLE DB Provider for ODBC (MSDASQL)
• IBM DB2 .NET Data Provider
• Microsoft OLE DB .NET Data Provider
• Microsoft ODBC .NET Data Provider
• Registering the DB2 Visual Studio Add-Ins
• Creating a Visual Basic ADO Application
• Creating a Visual C++ ADO application
• Creating a Visual Basic ADO.NET application
• Creating a Visual C# ADO.NET application
• Downloads
• Resources
• About the authors
• Comments

Next steps from IBM

• Try: DB2 Enterprise
• Demo: DB2 serving ATOM feed
• Webcast: A smarter way to successful SOA - Information as a trusted strategic asset
• Briefing: Information on Demand
• Buy: DB2 Enterprise

My developerWorks community

Dig deeper into Information Management on developerWorks

DB2 pureScale

See how true transparent scaling architecture can be achieved on distributed platforms

Special offers