hocheeming
Programmer
Hi everyone,
I am using ADO and is facing the "Operation not allowed when Object is closed" during my load test.
I had altogether 6 machines each running with 30 processes that calls the ADO api to retrieve records from a table to check on whether the recordset is empty or not.
After running the application for more than few hours... some machine will hit the "Operation not allowed when Object is closed" error just after the normal SQL query statement (like "select * from test"
which had shown to have created a recordset successfully and the ADO calls to check for whether the recordset is empty or not. This problem will then keep popping out on the machine itself.
I am using OLE DB with MDAC 2.6 SP2 on SQL 2000 server.
My question is does anyone has encountered such problem before? Is there anyway that I can perform more tracing on the SQL 2000 server or ODBC administrator to track on the problem?
Also I will like to find out on other alternatives to perform insertion of data using ADO. I am using a lousy method whereby I create a recordset by using
select * from test
and then
ADO addnew call to insert the record.
What other ways can I do to improve the performance?
Thank you.
Regards,
Chee Ming
I am using ADO and is facing the "Operation not allowed when Object is closed" during my load test.
I had altogether 6 machines each running with 30 processes that calls the ADO api to retrieve records from a table to check on whether the recordset is empty or not.
After running the application for more than few hours... some machine will hit the "Operation not allowed when Object is closed" error just after the normal SQL query statement (like "select * from test"
I am using OLE DB with MDAC 2.6 SP2 on SQL 2000 server.
My question is does anyone has encountered such problem before? Is there anyway that I can perform more tracing on the SQL 2000 server or ODBC administrator to track on the problem?
Also I will like to find out on other alternatives to perform insertion of data using ADO. I am using a lousy method whereby I create a recordset by using
select * from test
and then
ADO addnew call to insert the record.
What other ways can I do to improve the performance?
Thank you.
Regards,
Chee Ming