philjh
asked on
ADO.net general issue
I've just started getting my head around ADO.net and I can see the power of datasets for disconnected environments. However I can't quite see what the equivalent to an ADO CONNECTED recordset is. Surely on-line, concurrency/locked environments haven't disappeared overnight.
I would be grateful if someone would point me to a good article, or give me a brief rundown on the recommended approach to take using ADO.net for connected environments and the control for managing locking.
Cheers.
I would be grateful if someone would point me to a good article, or give me a brief rundown on the recommended approach to take using ADO.net for connected environments and the control for managing locking.
Cheers.
ASKER
I was starting to come to this conclusion.
So am I right in thinking that I should still be using ADO (not .net) for such connected requirements, or is there an ADO.net strategy which I could use as a work round.
Hope the COM-Interop is OK!
So am I right in thinking that I should still be using ADO (not .net) for such connected requirements, or is there an ADO.net strategy which I could use as a work round.
Hope the COM-Interop is OK!
ASKER
I was starting to come to this conclusion.
So am I right in thinking that I should still be using ADO (not .net) for such connected requirements, or is there an ADO.net strategy which I could use as a work round.
Hope the COM-Interop is OK!
So am I right in thinking that I should still be using ADO (not .net) for such connected requirements, or is there an ADO.net strategy which I could use as a work round.
Hope the COM-Interop is OK!
There is no work around. Sure you can still use ADO, but then you won't have the advantages of ADO.net. It's a design question.
CJ
CJ
ASKER
CJ
Sorry to push you on this but I do want to get this issue nailed down for myself (the points are yours).
If I absolutely must have the equivalent of a pessimistically locked recordset, I cannot have one from from ADO.net so must go to ADO? True/False?
Sorry to push you on this but I do want to get this issue nailed down for myself (the points are yours).
If I absolutely must have the equivalent of a pessimistically locked recordset, I cannot have one from from ADO.net so must go to ADO? True/False?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Unless your SQL Server is SQL Server.Net (I believe it is not out yet though)
ASKER
Seems like a bit of an overreaction from MS to the 'new world', when much of the world is still old.
Many thanks.
Many thanks.
I was quite astonished when I heard it at the Microsoft conference last year when they introduced ADO.Net... I just couldn't get my head over it, nor can I see the advantage of doing it that way.
You cannot do that anymore...
CJ