C
Cyril Gupta
I don't know if I am outdated or is my grouse still valid.
I am trying to connect two concurrent DataReader objects to the same
connection, but the attempt fails with the error "Another DataReader is
already open, it needs to be closed.. bla..bla.."
Using good old ADO I could connect as many Recordsets I wanted through one
connection, so how come ADO.Net is not allowing me to connect two
DataReaders?
I think I read somewhere that this can be done through .Net Framework 2.0.
Is this true? How stable is .Net 2.0? Are there any big issues that I should
know about?
My application will be distributed as a packaged software, so it should be
as stable as possible.
Please do send me your ideas.
Thanks
Cyril Gupta
I am trying to connect two concurrent DataReader objects to the same
connection, but the attempt fails with the error "Another DataReader is
already open, it needs to be closed.. bla..bla.."
Using good old ADO I could connect as many Recordsets I wanted through one
connection, so how come ADO.Net is not allowing me to connect two
DataReaders?
I think I read somewhere that this can be done through .Net Framework 2.0.
Is this true? How stable is .Net 2.0? Are there any big issues that I should
know about?
My application will be distributed as a packaged software, so it should be
as stable as possible.
Please do send me your ideas.
Thanks
Cyril Gupta