are you thinking of disconnected recordsets? if so the whole ADO.NET architecture operates on the disconnected model. Once you populate a dataset ADO.NET "disconnects" (sorry poor word here) from the underlaying database, and you work solely in memory. This is all good until you write back your changes to the database, then you have to start handling any changes that might have happened while you where playing with the data
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.