Feeds

Escape from Access DB

The relational database that polarises programmers

Top 5 reasons to deploy VMware with Tegile

Do you like Microsoft Access? Well, thanks to an intuitive and powerful user interface and being bundled as part of Office, it has established a niche for itself in many organisations, sometimes unofficially.

The combination of recordable macros, wizard-generated reports, query-by-example and, crucially, the provision of program support using Visual Basic for Applications has made MS Access the tool of choice for legions of developers of varying levels of ability and technical proficiency.

Not only has this led to a proliferation of applications, it has also produced a proliferation of "rescue" projects as those applications have grown in scope, size and complexity. For enterprise developers using Java this data need not remain out of reach thanks to the wonders of JDBC-ODBC bridges.

ODBC (Open Database Connectivity) is an API that provides programmatic access to data using SQL. ODBC adopts a layered approach; an application written to ODBC can talk to any underlying data source that has an ODBC driver. In the case of Access, ODBC support has been there almost from the beginning. In the Java world, a similar architecture exists called JDBC (Java Database Connectivity) in which Java applications written to the API can talk to any data source that has a JDBC driver. Put these together in the form of a JDBC-ODBC bridge and you have a platform-independent mechanism for Java to talk to any DBMS that has JDBC or ODBC drivers.

In the case of Access, the first step to opening the database to ODBC is to create an ODBC Data Source Name for your database. The simplest method is to load the Data Source Administrator from within the Windows Administrator tools (via the Control Panel if you're not running a server version of Windows).

A User DSN creates and registers a DSN for a single user, a System DSN is accessible to all users and a File DSN stores the DSN information to a file which can be shared among different users. In each case the DSN associates a user-defined label with a database driver (Microsoft Access Driver *.mdb) and a specific instance of the database. Once you create the DSN, any program that uses the ODBC API to talk to the underlying database can use it.

In the case of Java, the normal method for talking to a database is to use JDBC. First, the database driver is registered and then a specific database URL is used to establish a connection which can be used to create the statement object. Once this has been done, it's possible to interact with the database using SQL, stored procedures etc.

In the following code snippet, we are going to connect to an Access database which has a DSN of MyAccessDB using Sun's JDBC-ODBC bridge driver

import java.sql.*;

public class AccessDAO {

        private Connection con;
        private Statement st;
private static final String url="jdbc:odbc:MyAccessDB"; 
        private static final String className="sun.jdbc.odbc.JdbcOdbcDriver"; 
        private static final String user=""; 
        private static final String pass=""; 

        AccessDAO()throws Exception { 


        Class.forName(className); 
                con = DriverManager.getConnection(url, user, pass); 
                st = con.createStatement();  

                //do whatever database processing is required 
        } 
} 

It's not just the user data that can be queried using the JDBC-ODBC bridge, the database metadata can also be accessed. The following program will report all of the SQL data types supported by the version of Access used by the database contained in the MyAccessDB DSN:

import java.sql.*; 

public class AccessDAO { 

        private Connection con; 
        private Statement st; 
        private static final String url="jdbc:odbc:MyAccessDB"; 
        private static final String className="sun.jdbc.odbc.JdbcOdbcDriver"; 
        private static final String user=""; 
        private static final String pass=""; 
                
        public AccessDAO()throws Exception { 

                Class.forName(className); 
                con = DriverManager.getConnection(url, user, pass); 
                DatabaseMetaData dbMetaData  = con.getMetaData(); 
                ResultSet dbTypes = dbMetaData.getTypeInfo(); 
                String typeName; 
                System.out.println("Supported Database Types:"); 
                while (dbTypes.next()){ 
                        typeName = dbTypes.getString("TYPE_NAME"); 
                        System.out.println(typeName); 
                } 
                
        } 
        
        public static void main(String[] args) throws Exception{ 
                new AccessDAO(); 
        } 
        
} 

Of course, it's not just Access that supports ODBC. There are many other databases which support the ODBC API, and these aren't limited to the Windows operating system either. Furthermore, ODBC can be used with Excel and represents an alternative to the use of Apache POI or JExcelAPI as methods for interfacing Java and Excel. ®

Security for virtualized datacentres

More from The Register

next story
PEAK APPLE: iOS 8 is least popular Cupertino mobile OS in all of HUMAN HISTORY
'Nerd release' finally staggers past 50 per cent adoption
Microsoft to bake Skype into IE, without plugins
Redmond thinks the Object Real-Time Communications API for WebRTC is ready to roll
Microsoft promises Windows 10 will mean two-factor auth for all
Sneak peek at security features Redmond's baking into new OS
Mozilla: Spidermonkey ATE Apple's JavaScriptCore, THRASHED Google V8
Moz man claims the win on rivals' own benchmarks
FTDI yanks chip-bricking driver from Windows Update, vows to fight on
Next driver to battle fake chips with 'non-invasive' methods
DEATH by PowerPoint: Microsoft warns of 0-day attack hidden in slides
Might put out patch in update, might chuck it out sooner
Ubuntu 14.10 tries pulling a Steve Ballmer on cloudy offerings
Oi, Windows, centOS and openSUSE – behave, we're all friends here
Was ist das? Eine neue Suse Linux Enterprise? Ausgezeichnet!
Version 12 first major-number Suse release since 2009
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
New hybrid storage solutions
Tackling data challenges through emerging hybrid storage solutions that enable optimum database performance whilst managing costs and increasingly large data stores.
Getting ahead of the compliance curve
Learn about new services that make it easy to discover and manage certificates across the enterprise and how to get ahead of the compliance curve.