Thank you for the url, I will check it out later tonight. Perhaps I should explain abit what I want to do to make things clear on what I need to do.
My application is built on-top of a hierarchical object model and it also supports plug-ins. In the object model there might be a "collection" object called Employees which returns Employee objects. The Employees "collection" should fetch the data needed to return a correct Employee record when needed, since I dont want to pre-populate my object model to save resources. So instead of actually deriving a class from System.Collections.CollectionBase I need to write a "wrapper" class for a database connection and expose the normal methods and properties that a collection does, so it can act as if it was a normal collection (the plug-in developers etc shouldnt see the diffrence) What I mean with fresh data is that the application can be running on multiple machines that work on the same database, and if I were to pre-populate the object model instead of fetching the data when needed, then the changes thats been made by other instances of the application wont be used. Of course I know I need to ensure that not multiple instances of the application write over the same records and data is lost, but this is a diffrent subject. Ok so perhaps this helps shed some light on the subject, and can be of assistance when trying to offer me some help =) -- Andreas Håkansson Student of Software Engineering andreas (at) selfinflicted.org You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
