I think I did this once 12 years ago but today I wanted to test the accessibility of a SQL Server 6.5 database. After creating a ODBC datasource in Windows for the remote database, the following code ran perfectly. Recall that the JdbcOdbcServer.class is included in rt.jar so it is available without listing any jar in the classpath.
This proved to me that the database was not the issue causing the Windows 95 application to fail.
Past Blogs (Oldest to Newest)
- MySQL Quickstart
- Simple JUnit Example
- ANT's JavaDoc Task
- HSQLDB Console
- Elements of OO
- Variations on AS400 JDBC
- FTP Script
- Log4J Logs in DB/2
- Rhino Scripting in Java
- CSV Bulk Import
- JMock
- Internet Alphabet Soup
- Green Screen HTML Style
- Another Example - Yourself
- Groovy Script for AS400 Data
- Coad Interview of Jefferies
- More Scripting With Rhino
- Scripting With Objects
- Old School OO
- AS400 SYSPROCS
- Big Picture and Broken Windows
- Unheard Of! SQL on the AS400
- Behavioral Differences Between HashMap and TreeMap
- Sixty Second Rails
- Plum Pudding Model
- Impacting the Business
- CheatSheets
- Domain Modeling with Color?
- Maven Lifecycle and Examples
- Tomcat Basics
- Fitnesse How-To
- Ant's JAR Task
- Learning Tests for Java Dates
- Quickstart MySQL App With Maven
- Closures in Groovy
- Cohesion and Coupling
- Java Generics
- Groovy Script for Lucene
- Solient Green (and Architecture) is People
- Feeling Guilty?
- Subversion and Cruise Control
- Debugging RPG Called From JDBC
- The Value of Methodology
- Wicket in Action Quickstart
- Liquibase
- Inappropriate Infrastructure
- Idiomatic Ruby
- JRuby and Jetty
Blog Archive