To carry this on further, as I understand it....
You only need to implement Idisposable if you're going outside managed code to do something. For example, making a database connection, working with COM, etc. Otherwise, the class will cleanup on the next garbage collection.
>So the question as to why one should implement the Idisposable interface at all, is one needs it if one wants to use the "using" syntax. When you do that you get a class that cleans itself up just as nicely as ... a vfp class.
>
>From what I understand, without the "using" statements, the idisposable is decorative, errh, is need if one wants to conform to "official" standards. :)
>
>My 2 Eurocents.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer