qberta01
Programmer
- Nov 14, 2005
- 113
The issue occurs in the VB COM+ (VB6) objects that are using the ADODB.Recordset objects. We call a stored procedure (SQL 2000) through the ADODB.Recordset object, which normally returns a recordset back to us and we then loop through the object doing work. Except sometimes the recordset object comes back as closed - not simply empty, but actually closed. If you re-run the exact same project immediately after it, you will get results or at least an empty open recordset. This is so common that we actually have code in some places that checks for a closed recordset and re-passes the call through the DAL again.
What could be causing this? If anyone can assist me with this issue I would greatly appreciate it!
Thx!
What could be causing this? If anyone can assist me with this issue I would greatly appreciate it!
Thx!