Microsoft Corporation. Microsoft Open Database Connectivity Software Development Kit 2.0, Microsoft documentation, 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....a uniform code understandable by each other. This intermediate software layer often called middleware has to be sufficiently generic in order to allow a wide range of applications to interact. For the CQL card we have implemented an ODBC driver in conformity with the Microsoft ODBC specifications [ODBC93]. ODBC is the first implementation of the SQL Access Group (SAG) Call Level Interface (CLI) specifications for accessing to databases in heterogeneous environment. So, thanks to this consistency approach, we have a portable Windows software (ODBC is a part of the standard Windows and Windows NT ....

.... Implementation of the CQL ODBC driver To implement the CQL ODBC driver we have realize a Windows dynamic linked library (DLL) using the Microsoft ODBC Software Development Kit (SDK) set of software components and tools designed to help in developing ODBC drivers and ODBCenabled applications [ODBC93]. The CQL ODBC driver consists of two DLLs: CQLDRVSP.DLL : CQL driver setup program for specific installation and maintenance requirements of the CQL ODBC driver. This program is loaded when installing the CQL ODBC driver via the ODBC Setup and Administration utilities. CQLDRV.DLL : it is ....

[Article contains additional citation context not shown here]

Microsoft Corporation. Microsoft Open Database Connectivity Software Development Kit 2.0, Microsoft documentation, 1993.

....distribution for the MSDN Corporate Benefits Sample. As shipped, Benefits can be distributed as either a 2 tier or a 3 tier client server application. The 2 tier implementation places the Visual Basic front end and the business logic components on the client and the database, accessed through ODBC [28], on the server. The 3 tier implementation places the front end on the client, the business logic on the middle tier, and the database on the server. Coign cannot analyze proprietary connections between the ODBC driver and the database server. We therefore focus our analysis on the distribution of ....

Microsoft Corporation. Microsoft Open Database Connectivity Software Development Kit. Version 2.0. Microsoft Press, 1994.

....criteria include these: no changes to the underlying DBMS, retention of all desired properties of the DBMS, and minimal impact on middleware. We then define three overall architectures to building a stratum, namely (a) imposing a stratum directly, b) using middleware as the stratum (e.g. ODBC [14]) and (c) using a preprocessor. Each overall architecture captures several specific architectures, which are discussed in turn. We use the architectures for classifying existing systems, including the temporal DBMS implementations listed in a resent survey [5] The specific architectures are then ....

....that uses the DBMS directly. It is important that the stratum does not require the DBMS to be modified because we do not have the source code for the DBMS available. 2. Minimal impact on middleware. The stratum may not use the DBMS s native CLI, but may instead use a generic API, e.g. ODBC [14]. We allow changes to this middleware, which can be used in the implementation of the stratum (to be discussed in Section 3.2) because generic APIs are open standards with source code available. An example can be to change the middleware to initiate a temporal SQL to SQL 92 conversion. The ....

[Article contains additional citation context not shown here]

Microsoft Corp. Microsoft Open Database Connectivity Software Development Kit Version 2.0. Microsoft Press, 1994.

....to a procedure that analyses the strings and executes the statements described by them. For example, one can write conn.Prepare( CREATE TABLE Persons FOR Person ) without needing a language extension nor a preprocessor. We implemented a module ESQL [Ste96a] that provides access to ODBC databases [ODBC94]. DEFINITION ESQL; CONST ( return codes ) InvHandle = 2; Error = 1; Success = 0; SuccessWithInfo = 1; NoDataFound = 100; TYPE Connection = POINTER TO ConnectionD; ConnectionD = RECORD ret: INTEGER; return code of last operation ) PROCEDURE (c: Connection) Prepare (sqlStr: ARRAY OF ....

Microsoft Open Database Connectivity Software Development Kit Version 2.0, Microsoft Press, 1994.

....rely on the relational data model. The former is a topic of heavy research, the latter is heavily used. This report describes our support to access ODBC databases, which become widely used under MS Windows and other operating systems. 4 2. Background 2. 1 ODBC ODBC (Open Database Connectivity) [ODBC94] is Microsoft s implementation of the SQL Connectivity specification [Mel93] ODBC defines functions that allow an application to connect to a database, to execute SQL statements, and to retrieve the results. Furthermore it defines standard error codes and standard data types. Many existing ....

....relation: Class methods: Method Italic font: Uses relation: employer employee abstract method, abstract class Figure 4. Classes and their defining modules 8 4. Module ODBC Module ODBC contains declarations of types, constants, and procedures that are available in Microsoft s ODBC interface [ODBC94]. It is essentially a 1 to 1 mapping of the dynamically loadable library ODBC32.DLL that implements the ODBC driver manager under MS Windows. Therefore ODBC programs written in other programming languages can easily be ported if they rely only on the ODBC32.DLL. The interface of the module has ....

Microsoft Open Database Connectivity Software Development Kit Version 2.0, Microsoft Press, 1994.

....Benefits Sample. As shipped, Benefits can be distributed as either a 2 tier or a 3 tier client server application. In the 2 tier scenario, the Visual Basic front end and the business logic components are located on the client while the database is located on the server and accessed through ODBC [9]. In the 3 tier scenario, the Visual Basic frontend is located on the client, the business logic components are located on the middle tier, and the database is located on the server. Coign cannot analyze proprietary connections between the ODBC driver and the database server. We therefore focus ....

Microsoft Corporation. Microsoft Open Data- base Connectivity Software Development Kit. Version 2.0. Microsoft Press, 1994.

....which can even run on a different machine connected with the client via a network. Furthermore it is not necessary that the application knows the database in advance (as it is with Embedded SQL) The result is a gain in database independence and interoperability. 2 Background 2. 1 ODBC ODBC [ODBC94] is Microsoft s implementation of the SQL Connectivity specification [SQL CLI] which they jointly developed with Lotus, Sybase, and DEC. The ODBC library contains function calls that allow an application to connect to a DBMS, execute SQL statements, and retrieve results. Furthermore it defines ....

Microsoft Open Database Connectivity Software Development Kit Version 2.0. Microsoft Press, 1994, ISBN 1-55615-658-8

....on a different machine connected with the client via a network. Furthermore it is not necessary that the application knows the database in advance (as it is with Embedded SQL) The result is a gain in database independence and interoperability. 1 DBMS database management system 2 ODBC ODBC [ODBC94] is Microsoft s implementation of the SQL Connectivity specification [SQL CLI] which they jointly developed with Lotus, Sybase, and DEC. The ODBC library contains function calls that allow an application to connect to a DBMS, execute SQL statements, and retrieve results. Furthermore it defines ....

Microsoft Open Database Connectivity Software Development Kit Version 2.0. Microsoft Press, 1994, ISBN 1-55615-658-8

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC