ResultSets are *sets* of objects and do not point to a record but a *set* of records. Think of it like opening a pointer to a shelf in a library. Whether there's one record or hundreds, initially the result set only points to the shelf.
In order to view the contents of the shelf you need to iterate over it using result.next(). Each time this is called the pointer is moved from book to book in order they were retrieved from the database and if result.next() ever returns false it means there are no more books. For your situation, if you are expecting exactly one result than you should have code like this:
[ January 18, 2007: Message edited by: Scott Selikoff ]
Originally posted by Malith Yapa: SQL data is case sensitive..
Actually, I believe case sensitivity is a feature in some databases and by default you can specify matches as being case sensitive and case insensitive.
Either way, the better form would be: For the most part "OR" should be avoided at all costs in SQL since they can seriously hurt performance if used poorly in joins. [ January 20, 2007: Message edited by: Scott Selikoff ]