109 lines
5.7 KiB
HTML
109 lines
5.7 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Choose an interface to access the ODBC driver" />
|
||
|
|
<meta name="abstract" content="There are different programming interfaces that can be used with the iSeries Access for Windows ODBC Driver. Each interface has its strengths and weaknesses." />
|
||
|
|
<meta name="description" content="There are different programming interfaces that can be used with the iSeries Access for Windows ODBC Driver. Each interface has its strengths and weaknesses." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcapiinfo.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="odbcinterfaces" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Choose an interface to access the ODBC driver</title>
|
||
|
|
</head>
|
||
|
|
<body id="odbcinterfaces"><a name="odbcinterfaces"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Choose an interface to access the ODBC driver</h1>
|
||
|
|
<div><p>There are different programming interfaces that can be used with
|
||
|
|
the iSeries™ Access
|
||
|
|
for Windows<sup>®</sup> ODBC
|
||
|
|
Driver. Each interface has its strengths and weaknesses.</p>
|
||
|
|
<div class="section"><p>Three of the more common programming interfaces are ActiveX Data
|
||
|
|
Objects (ADO), Rapid Application Development (RAD) tools, and ODBC APIs.
|
||
|
|
The supported languages, reasons for using, and sources of more information
|
||
|
|
for these three interfaces, are provided below.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">ActiveX Data Objects (ADO)</h4><p>ADO refers to ActiveX Data
|
||
|
|
Objects and is Microsoft's high level object model for data access. </p>
|
||
|
|
<ul><li>Supported programming languages: <ul><li>Visual Basic</li>
|
||
|
|
<li>Active Server Pages (ASP)</li>
|
||
|
|
<li>Delphi</li>
|
||
|
|
<li>Visual Basic Script</li>
|
||
|
|
<li>any other language or script that supports ActiveX or COM</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Reasons to use this method: <ul><li>Eliminates the coding of ODBC APIs</li>
|
||
|
|
<li>Supports switching providers, when needed</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Where to go for more information: <ul><li>More on how to use ADO, see the ADO documentation that comes in MDAC:
|
||
|
|
www.microsoft.com/data/doc.htm </li>
|
||
|
|
<li>More on using the iSeries Access OLE-DB Provider through ADO refer
|
||
|
|
to:<a href="rzaikoledbprovider.htm#oledbprovider">iSeries Access for Windows OLE DB provider</a></li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Special notes: <ul><li>To use ODBC through ADO an application needs to specify the MSDASQL provider
|
||
|
|
in a connection string. MSDASQL converts ADO calls into ODBC API calls which
|
||
|
|
communicate with the ODBC driver.</li>
|
||
|
|
<li>An example using an ADO connection string follows: <p> ConnectionString = "Provider=MSDASQL;Data Source=MYODBCDS;"</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Rapid Application Development (RAD) tools</h4><p>Rapid
|
||
|
|
Application Development tools are tools that help in creating applications
|
||
|
|
quickly. The tools make it so that the application writer does not have to
|
||
|
|
know much about the ODBC specification. </p>
|
||
|
|
<ul><li>Supported programming languages: <ul><li>Depends on which RAD tool is used. </li>
|
||
|
|
<li>Some of the more commonly used tools include Powerbuilder, Delphi, and
|
||
|
|
Seagate Crystal Reports.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Reasons to use this method: <ul><li>Eliminates the coding of ODBC APIs</li>
|
||
|
|
<li>Works with multiple ODBC drivers using one program, with few or no changes</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Where to go for more information: <ul><li>Refer to the documentation included with the RAD tool.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Direct ODBC API calls</h4><p>Direct ODBC API calls are
|
||
|
|
when an application is written directly to the ODBC specification.</p>
|
||
|
|
<ul><li>Supported programming language: <p>C/C++</p>
|
||
|
|
</li>
|
||
|
|
<li>Reasons to use this method: <ul><li>Allows direct control over which ODBC APIs are called so can be faster
|
||
|
|
than using ADO objects or RAD tools</li>
|
||
|
|
<li>Designed to take advantage of driver-specific features</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Where to go for more information: <ul><li>For information on the ODBC specification and some samples see the ODBC
|
||
|
|
documentation that comes in MDAC: www.microsoft.com/data/doc.htm. </li>
|
||
|
|
<li>For more information about driver-specific features see <a href="rzaikodbcapifunctions.htm#odbcapifunctions">Implementation issues of ODBC APIs</a></li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikodbcapiinfo.htm" title="Identify the files required to build an ODBC application.">Files required to build an ODBC application</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|