This tutorial describes how you can build a .NET application that uses the Oracle Data Provider for .NET to access data in an Oracle Database.
Approximately 30 minutes
In addition to basic Oracle client connectivity software,
.NET applications require the use of what is known as a managed data provider
(where "managed" refers to code managed by the .NET framework). The data provider
is the layer between the .NET application code and the Oracle client connectivity
software.
The Oracle Data Provider for .NET (ODP.NET) is Oracle's high performance ADO.NET
2.0 compliant data provider that exposes a complete set of Oracle specific
features and tuning options including support for Real Application Clusters,
XML DB, and advanced security. It is available for free download from the
Oracle Technology Network website.
When ODP.NET and any required Oracle client connectivity software is installed,
application development using Visual Studio can begin. It is a good idea
to confirm client connectivity before starting development. If you can connect
to Oracle using SQL*Plus on the same machine as Visual Studio, then you know
that your Oracle client-side software is properly installed and configured.
Before starting this tutorial, you should:
. |
Install Microsoft Visual Studio 2010 |
---|---|
. |
Install Oracle Database 9.2 or later or Oracle Database XE |
. |
Install Oracle 11g Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio version 11.2.0.1.2 or later from OTN |
To create a new project in Visual Studio, perform the following steps:
. |
From your Windows Program menu, start Visual Studio. From the File menu, select New Project.
|
---|---|
. |
From the Project types list, select Visual Basic: Windows. Select the Template Windows Form Application. In the Name field, enter OraWinApp. In the Location field, enter the directory where you want to save the files. (Note: if the directory does not exist, it is created). Click OK
|
. |
The project has been created. From View menu, select Solution Explorer to open the Solution Explorer if not already open.
|
Because your project needs access to an Oracle database, it is necessary to add a reference to the dll containing the data provider. Perform the following steps:
. |
From Project menu, select Add Reference...
|
---|---|
. |
Scroll down the list of Component Names and select Oracle.DataAccess. Click OK.
|
To retrieve data from the database, you can add some controls to your form. Perform the following steps:
. |
From View menu, select Toolbox. The toolbox appears. Expand Common Controls.
|
---|---|
. |
Drag the Button control to the Form1 canvas. The control is shown on the canvas. You also need to create a Label.
|
. |
From the Toolbox, drag the Label control to the Form1 canvas.
|
. |
Double-click Button1 to open the code window. Note, Form1.vb code window opens.
|
. |
Add the following VB.NET Imports statements before the Public Class declaration. Imports System.Data
|
. |
Add the following VB.NET code between the Private Sub and End Sub statements. Dim oradb As String = "Data
Source=orcl;User Id=hr;Password=hr;"
|
. |
Select Build > Build OraWinApp. In the output window, ensure you did not get any errors. Now you can run the form.
|
. |
Select Debug > Start Without Debugging.
|
. |
The form appears. Click button1. The result is shown in the label. Since the query in the code was to show the department name for department id of 10, the result is the Administration department. Close Form1.
|
Instead of running the hard coded query, you can add a textbox control to accept user input for the department id. Perform the following steps:
. |
Select the Form1.vb [Design] tab. From the Toolbox, drag the TextBox control to Form1 canvas. The textbox is shown. You can drag it to the desired location.
|
---|---|
. |
Drag a Label control on Form1 canvas.
|
. |
The Label is shown. Right-click Label2 and select Properties.
|
. |
In the Properties sheet, change the Text property to Enter Department ID:
|
. |
Select the Form1.vb tab.
|
. |
You use a bind variable to include the value of the text box as part of the SELECT statement. Bind variables improve performance by preventing the database from having to reparse the SQL statement every time the text box value changes. Add the following code right after the conn.Open() statement: Dim parm As New OracleParameter
|
. |
Add the cmd.Parameters statement right after the cmd.Connection statement: cmd.Parameters.Add(parm)
|
. |
Change the code for the cmd.CommandText statement to the following: cmd.CommandText = "select department_name from departments where department_id = :1"
|
. |
Select Build > Rebuild OraWinApp. Check in the output window for any errors reported. If no errors or warnings, proceed with the next step.
|
. |
Select Debug > Start Without Debugging.
|
. |
Enter 20 for the Department ID and click button1.
|
. |
Notice that the Label1 changes to the name of the department. This value depends on what is entered in the Department ID field.
|
. |
Enter 300 for the Department ID and click button1.
|
. |
This time you receive an error because there is no department with the id of 300. Click Quit. In the next topic you add some error handling so you know exactly why you received the error.
|
Error handling is needed to instruct the user why something doesn't work properly. In this topic, you modify your code to prevent an error when an invalid Department ID is provided. In this tutorial, you add some very simple error handling code. For more robust error handling, Structured Exception Handling should be used. For more information on Structured Exception Handling with ODP.NET please refer to the ODP.NET online documentation. Perform the following steps:
. |
In Form1.vb window, change the following code from: dr.Read() label1.Text = dr.Item("department_name"); to If dr.Read() Then Label1.Text = dr.Item("department_name") Else Label1.Text = "Department ID not found" End If
|
---|---|
. |
Select Build > Rebuild OraWinApp. Ensure that there are no errors reported in the output window.
|
. |
Select Debug > Start Without Debugging.
|
. |
Enter 300 again for the Department ID and click button1.
|
. |
This time, the message Department ID not found is displayed. Close Form1.
|
In this topic, you want to retrieve more than one set of information using a listbox. Perform the following steps:
. |
Click the Form1.vb [Design] tab. From the Toolbox, drag the Listbox control to the Form 1 canvas.
|
---|---|
. |
The new listbox appears on the form. You can position and re-size the listbox appropriately. Click Form1.vb tab.
|
. |
Delete the cmd.Parameters.Add(parm); statement.
|
. |
Change the cmd.CommandText code from: cmd.CommandText = "select department_name from departments where department_id = :1"; to cmd.CommandText = "select
department_id, department_name, city"
|
. |
Also change the following lines of code from: If dr.Read() Then to While dr.Read()
|
. |
Select Build > Rebuild OraWinApp.
|
. |
Select Debug > Start Without Debugging.
|
. |
Click button1.
|
. |
The list of all the departments and their location is shown. Close Form1. |
In this tutorial, you have learned how to:
About Oracle |Oracle and Sun | | Careers | Contact Us | Site Maps | Legal Notices | Terms of Use | Your Privacy Rights | |