This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
"gsk", The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at http://www.javaranch.com/name.jsp . We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please re-register and select a new name which meets the requirements. Thanks. Dave
Sorry about that, I like getting the book-keeping out of the way first. When you use a driver, you rely on it to implement the entire JDBC API. The problem is, quite often they don't. Sounds like you are trying to use a method that should exist (according to the API) but hasn't been written in your driver. If you are using the jdbc-odbc bridge it gets much worse, since I'm pretty sure this only implements a small part of the JDBC 2.0 API. Your options are to either live without the extra functionality (ie use ResultSet.next() and close() only) or use the specific Type 4 Driver for your database (unless you're using Access, in which case you should use something else) Dave.