Null consistently returned by RecordSet.getTimeStamp()

Question

Hi
I'm continually getting 'null' being returned by the getTimeStamp(int) method from a ResultSet.
If I run the stored proc with the required parameters in SQL server, it returns values for the field. Its a DateTime field - so should return this when my code calls it, right?
Here is a snippet of the code:
      try {             conn = datasrc.getConnection();             cs = conn.prepareCall("{call rsp_employee_get(?,?)}");             cs.setInt(1, id);             cs.setString(2, name);             rs = cs.executeQuery();             if(rs.next()) {                                 employee = new Employee();                 employee.setManagerId(rs.getInt(1));                 employee.setOccupationId(rs.getInt(2));                 employee.setJobTitle(rs.getString(3));                 employee.setPreferredName(rs.getString(4));                 employee.setWorkedFromDate(rs.getTimestamp(5));                 employee.setWorkedToDate(rs.getTimestamp(6));            //this is where my error occurs
All objects etc have been created correctly, and obviously above is only a snippet.
The proc returns values as expected, and rs.getTimestamp(5) works fine - however these dates all have the time 00:00:00.000 whereas the field getTimestamp(6) refers to have times of 23:59:59.000... (could this be it??)
The proc returns a list of employees off the database, past and present - so some do have null values for this field (ie they're current employees) - however, I've checked and its recording them all as null even though they're not null when I run the proc manually.
I'm getting a bit fed up with it to be honest, hoping someone here has seen it before and can see if I've done something wrong?

Answer 1

On my production system the same query processes just fine...EXCEPT that the Recordset is "n/a".
Can you clarify what you mean by "n/a"?
I can't see how it would make a difference, but you should not hard-code dynamic values into you SQL statement, you should pass them as a parameter.
So it would seem that it's a CF problem... agree?
Nope.  CF doesn't know or care about your SQL.  All it does is pass it to the DB driver, and wait for the DB driver to return something to it.
That said, it might not be a problem with the call, it might be a problem with how it handles what it gets back, I suppose.
Running with that theory... I wonder if the change to the ORDER BY statement is coincidental, perhaps it's just that it bubbles to the top of the recordset something that CF doesn't like.  Can you remove columns from you SELECT statement one by one, and see if at some point if starts returning data correctly?
Can you do a trace on the query and verify what the DB is receiving from the driver, and what it's sending back?  I have no idea how to do that in SQLite, sorry.
Adam