Besides closing the connection, is there any other cleanup
I should be doing for the adapter, dataset, datatable and
commandbuilder objects upon application exit?

Closingthe Connection is all that's required. However, some will argue that
closing and destroying all of your objects explicitly makes your code neater
and easier to read...

--
Carsten Thomsen
Enterprise Development with Visual Studio .NET, UML, and MSF
http://www.apress.com/book/bookDisplay.html?bID=105
"Tom Archer" <(E-Mail Removed)> wrote in message
news:84cc01c35ac7$28483b40$(E-Mail Removed)...
> Besides closing the connection, is there any other cleanup
> I should be doing for the adapter, dataset, datatable and
> commandbuilder objects upon application exit?

I would argue it makes it harder to read, because then it gets cluttered
with lines that just set various objects to Nothing, etc.

"CT" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Closingthe Connection is all that's required. However, some will argue
that
> closing and destroying all of your objects explicitly makes your code
neater
> and easier to read...
>
> --
> Carsten Thomsen
> Enterprise Development with Visual Studio .NET, UML, and MSF
> http://www.apress.com/book/bookDisplay.html?bID=105
> "Tom Archer" <(E-Mail Removed)> wrote in message
> news:84cc01c35ac7$28483b40$(E-Mail Removed)...
> > Besides closing the connection, is there any other cleanup
> > I should be doing for the adapter, dataset, datatable and
> > commandbuilder objects upon application exit?
>
>

I agree. In my case, I would be inserting several lines of
code in the view's OnDestroy function that would simply
set various objects to NULL on the way out of the
application. This would be very misleading to someone
reading the code and definitely make them think this is a
necessary step when in fact it appears (from what you guys
are saying) that ADO.NET object clean-up is automatic.

>-----Original Message-----
>I would argue it makes it harder to read, because then it
gets cluttered
>with lines that just set various objects to Nothing, etc.
>
>"CT" <(E-Mail Removed)> wrote in
message
>news:(E-Mail Removed)...
>> Closingthe Connection is all that's required. However,
some will argue
>that
>> closing and destroying all of your objects explicitly
makes your code
>neater
>> and easier to read...
>>
>> --
>> Carsten Thomsen
>> Enterprise Development with Visual Studio .NET, UML,
and MSF
>> http://www.apress.com/book/bookDisplay.html?bID=105
>> "Tom Archer" <(E-Mail Removed)> wrote in message
>> news:84cc01c35ac7$28483b40$(E-Mail Removed)...
>> > Besides closing the connection, is there any other
cleanup
>> > I should be doing for the adapter, dataset, datatable
and
>> > commandbuilder objects upon application exit?
>>
>>
>
>
>.
>