Guide to Oracle 11g and Database Migration
Oracle Database 11g includes more features for self-management and automation, which makes it easier for customers to cost-effectively manage their data. Download this Internet.com eBook for an overview of some of the new features in 11g and for an overview of the issues you need to consider as you prepare for a database migration.
»
Innovate Faster with Oracle Database 11g
Read this in-depth analysis of 56 customers, which shows significant differences between the value software vendors Oracle and SAP deliver to midsize companies.
»
Oracle Business Intelligence Standard Edition One
Find out how Newport Beach, CA-based Mobilitie is shaking up the telecom industry by leveraging technology to provide an entirely different financial model for deploying, upgrading, and owning wireless and wireline network assets.
»
Business Intelligence and Enterprise Performance Management: Trends for Emerging Businesses
Quickly implementing an ERP software solution can be of tremendous benefit; however, companies often struggle to balance the benefits of reducing implementation time and cost with the risks of an accelerated deployment. Read this white paper to learn about easy-to-follow best practices for achieving a successful accelerated implementation.
»
August 7, 2001 ODBC DSN-Less Connection Tutorial By Danny Lesandrini
What is DSN-Less ODBC?
In a previous article, Problematic or Programmatic ODBC, I described
the various ways I have used to distribute a DSN (ODBC Data Source Name) to users of my client/server
applications. Towards the end of that article, I mentioned an Access Database Application I created
to serve as a tutorial for people with questions about reconnecting linked MS Access tables to SQL
Server using DSN-Less ODBC. This article will focus on the details of that tutorial, which is
available for download.
DSN-Less ODBC simply means that instead of storing connection information (like server, database, etc.)
in a file or the Windows Registry, you have plunked them into a connect string, which is then associated
with some data object, like an Access linked table. Here is an example of the connect string generated
by my tutorial:
In our example, the DRIVER parameter will always be SQL Server, so the Login form doesn't need to
bother the user for that information. On the other hand, the other arguments are subject to change,
so the user needs to be queried to supply the SERVER, DATABASE, USER and PASSWORD. In most cases, the
user is required to supply some or all of these values. The Access form which I use to collect this
information looks like this:
Making it Easier for the User
Since login screens can be intimidating for some users, I decided to add an optional "auto-populate"
feature to the login form. Instead of supplying the user with values which need to be typed into the
login form, the user simply supplies the path to a file (an old-fashioned ini file) containing that
information. In our application, that path was hidden from the user and login was truly automatic.
This idea worked well for us, since it was customary to create a common network folder
where application setup and shared files could be accessable to all users. In order to automate the
login process, the application adminstrator needs simply to edit the ini file with current data source
information.
Add databasejournal.com to your favorites Add databasejournal.com to your browser search box IE 7 | Firefox 2.0 | Firefox 1.5.xReceive news via our XML/RSS feed