ResultSet: SQLException when send to another class

Question

Hi everyone,
This simplified version of my code compiles but I get "SQLException: Invalid Descriptor Index" in setData() at runtime. I still get the same problem when I put ClassA and ClassB in the same package.
rsResult has valid data in ClassA but rsResult in setData() seems to have no data at all. Any help on this would be greatly appreciated. - Howard
package com.PK;
public class ClassA
funtion MyFunc()
       Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
            err = err + " Loaded sun.jdbc.odbc.JdbcOdbcDriver ";       
        //verify driver is valid
        if (DriverManager.getDriver("jdbc:odbc:History").jdbcCompliant())
                con = DriverManager.getConnection("jdbc:odbc:History");                   
                String strSql = "{call sproc_getData()}";
                cs = con.prepareCall(strSql);
.prepareCall(strSql);               
                 cs.execute();               
                 rsResult= cs.getResultSet();
                 ClassB cB = new ClassB();
                 while(rsResult.next())
                  System.out.println("before send" + rsResult.getString("Symbol")); // good data
                   cB.setData(rsResult);
package com.PK.History; //error
//package com.PK; //also error
ClassB
   public void setData(ResultSet rsResult)
            System.out.println("setData:in" + rsResult.getString(1)); // error
            //System.out.println("setData:in" + rsResult.getString("Symbol")); //also error.
}

Answer 1

I did read the columns in sequence. Also, I did not
close the statement or connection.Not in the code you posted, you didn't. You called rs.getString("Symbol") and then rs.getString(1). That can't be "in sequence".
After more testing, it turned out that this code
works if I use ClassB directly. (Abtract Factory
pattern) I was using ClassB's Factory interface class.This suggests to me that your code is a mess. If changes like that break your JDBC code then you need to clean it up. In general if you find yourself passing ResultSets as parameters to methods in other classes, that's a symptom that your JDBC code is all over the place.