SQLException No ResultSet set was produce

[rajamohammed]

Hi Everyone,
I am gettiing exception while deleting a record,that
java.sql.SQLExc eption: [Microsoft][SQLServer 2000 Driver for JDBC]No ResultSet set was produced.
But the record is deleted successfully. Please help me.

Thanks,
Raja Mohammed

[JosAH]

Hi Everyone,
I am gettiing exception while deleting a record,that
java.sql.SQLExc eption: [Microsoft][SQLServer 2000 Driver for JDBC]No ResultSet set was produced.
But the record is deleted successfully. Please help me.

Thanks,
Raja Mohammed

Show us a bit of code please; to me it makes sense that no ResultSet was
produced because you deleted a record (which worked as you wrote) but I
suspect you still want to do something with that (non-existent) ResultSet.

kind regards,

Jos

[praveen2gupta]

Hi Everyone,
I am gettiing exception while deleting a record,that
java.sql.SQLExc eption: [Microsoft][SQLServer 2000 Driver for JDBC]No ResultSet set was produced.
But the record is deleted successfully. Please help me.

Thanks,
Raja Mohammed

Hi
Your error is absolute right. Resultset is required for the select command only. When data is coming from table to the web page. while for delete,update and insert operations you required to executeUpdate only. There is no role of Resultset in these cases. In these command you are performing operation on the tables.

[rajamohammed]

Hi
Your error is absolute right. Resultset is required for the select command only. When data is coming from table to the web page. while for delete,update and insert operations you required to executeUpdate only. There is no role of Resultset in these cases. In these command you are performing operation on the tables.

Hi JosAH, Praveen,
Thanks for your help. previously I used executeQuery. Now I used excuteUpdate. Now the exception is not coming, Thanks a lot.
-Raja Mohammed

[santhosh ch]

Hi all. This article helped me when i was searching for this exception.

--Santhosh ch

[surindersingh]

Thanks everyone. This post helped me in hunting down the issue

[jenishca]

use executeUpdate instead of executeQuery