|
OpenAccessTM
SDK provides the toolkit and the run-time
software components needed to implement an OLE DB
provider, ODBC driver or a JDBC driver for your data
source within weeks - easily enable your data source to
plug and play in Microsoft's Universal Data Access (UDA)
strategy. The toolkit is used to build an Interface
Provider (IP) to your data source through the
implementation of a defined API consisting of 10
functions.
OpenAccess SDK is suited for making desktop or server
based data sources accessible through JDBC, ODBC or OLE
DB. It provides 90% of the code that is required to open
up a database. The other 10% of the code resides between
our SQL engine and your database. This is the code you
write to take information from the SQL engine and to use
it to process rows of data from your database. You write
your code with very little concern for the JDBC, ODBC or
OLE DB interfaces, SQL, networking, optimization, data
types and many other issues. Don't worry about taking a
request to process data; we provide you all the
information you need to do it optimally.
With OpenAccess SDK, developing robust, high-performance
JDBC, ODBC or OLE DB drivers is as easy as A - B - C.
A) Just concentrate on how you want to model your data -
the schema definition.
B) Write the code to access your data and format into row
data structures - we let you use C, C++, or COM. This code
you write is what we call the Interface Provider or IP. It
can make use of your existing libraries and business
objects (COM or JAVA).
C) Call us if you have any questions. That's it - now you
are ready to ship.
As you can see, we require no knowledge of SQL, ODBC, OLE
DB, COM or networking. This is all hidden from the IP, so
there is no need to learn SQL, ODBC, OLE DB, COM or
networking.
In the client/server configuration, the OpenAccess ODBC, or
the OLE DB component, runs on one system and the server
portion runs on the system containing the database. To
make your data source accessible over a network, all you
have to do is develop a driver (IP) for your data source.
All client/server communication issues are handled by the
OpenRDA client/server components.
With OpenAccess SDK, the code you write can be used unchanged
to support both native OLE DB and native ODBC. In
client/configuration, the same server you build can be
accessed from native ODBC and native OLE DB drivers and
from JDBC. OLE DB implementors can take advantage of
VARIANT and other features.
|
Features
-
OLE DB and ODBC drivers comply with Microsoft specifications for OLE DB and ODBC
-
JDBC driver complies with Sun's JDBC specifications
-
Optimizing SQL engine
-
Full SQL capability including JOINS, user definded scalar function, stored procedures, views, access controls and much more
-
You need to implement just 10 functions that deal with the physical data access
-
Supported on over 13 different platforms including SCO OpenServer
-
Client/server architecture for optimized data access and processing
-
ODBC client drivers available on over 13 platforms
-
Fully threaded for performance and scalability
-
Many examples available to allow you to quickly develop your driver
|
