"tshad" <t**@dslextreme.com> wrote in message
news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
>I have been misunderstanding the closing of the connection.
>
> If I have set CommandBehavior.CloseConnection, I thought that connection
> would be closed when you had read through the dataread.  As a matter of
> fact
> I found that if I had it set, I couldn't seem to get to the next results,
> if
> there were multiple results (NextResult() would give me an error).
>
> Now I find that I need to close the Reader to close the connection.
>
> This is a problem with my Database object.  I have an object
> (RunProcedure)
> that executes a stored procedure and then returns a DataReader.  I have
> the
> reader set to CommandBehavior.CloseConnection.  This would be ok as I can
> close the DataReader, which should close the connection if I do a:
>
> dbReader = RunProcedure(...)
> dbReader.Close()
>
> But how do I deal with (or can I) the situation where I do a direct
> Databind
> to Grid, listbox, etc?
>
> DataGrid1.DataSource = RunProcedure()
>
> I have no DataReader to close.
>
> Thanks,
>
> Tom
>
>

"tshad" <t**@dslextreme.com> wrote in message
news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
>I have been misunderstanding the closing of the connection.
>
> If I have set CommandBehavior.CloseConnection, I thought that connection
> would be closed when you had read through the dataread.  As a matter of
> fact
> I found that if I had it set, I couldn't seem to get to the next results,
> if
> there were multiple results (NextResult() would give me an error).
>
> Now I find that I need to close the Reader to close the connection.
>
> This is a problem with my Database object.  I have an object
> (RunProcedure)
> that executes a stored procedure and then returns a DataReader.  I have
> the
> reader set to CommandBehavior.CloseConnection.  This would be ok as I can
> close the DataReader, which should close the connection if I do a:
>
> dbReader = RunProcedure(...)
> dbReader.Close()
>
> But how do I deal with (or can I) the situation where I do a direct
> Databind
> to Grid, listbox, etc?
>
> DataGrid1.DataSource = RunProcedure()
>
> I have no DataReader to close.
>
> Thanks,
>
> Tom
>
>

>
> hth
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
>
> "tshad" <t**@dslextreme.com> wrote in message
> news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
> >I have been misunderstanding the closing of the connection.
> >
> > If I have set CommandBehavior.CloseConnection, I thought that connection
> > would be closed when you had read through the dataread.  As a matter of
> > fact
> > I found that if I had it set, I couldn't seem to get to the next
results,
> > if
> > there were multiple results (NextResult() would give me an error).
> >
> > Now I find that I need to close the Reader to close the connection.
> >
> > This is a problem with my Database object.  I have an object
> > (RunProcedure)
> > that executes a stored procedure and then returns a DataReader.  I have
> > the
> > reader set to CommandBehavior.CloseConnection.  This would be ok as I
can
> > close the DataReader, which should close the connection if I do a:
> >
> > dbReader = RunProcedure(...)
> > dbReader.Close()
> >
> > But how do I deal with (or can I) the situation where I do a direct
> > Databind
> > to Grid, listbox, etc?
> >
> > DataGrid1.DataSource = RunProcedure()
> >
> > I have no DataReader to close.
> >
> > Thanks,
> >
> > Tom
> >
> >
>
>

>
> >
> > hth
> >
> > --
> > ____________________________________
> > William (Bill) Vaughn
> > Author, Mentor, Consultant
> > Microsoft MVP
> > INETA Speaker
> > www.betav.com/blog/billva
> > www.betav.com
> > Please reply only to the newsgroup so that others can benefit.
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > __________________________________
> >
> > "tshad" <t**@dslextreme.com> wrote in message
> > news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
> > >I have been misunderstanding the closing of the connection.
> > >
> > > If I have set CommandBehavior.CloseConnection, I thought that
connection
> > > would be closed when you had read through the dataread.  As a matter
of
> > > fact
> > > I found that if I had it set, I couldn't seem to get to the next
> results,
> > > if
> > > there were multiple results (NextResult() would give me an error).
> > >
> > > Now I find that I need to close the Reader to close the connection.
> > >
> > > This is a problem with my Database object.  I have an object
> > > (RunProcedure)
> > > that executes a stored procedure and then returns a DataReader.  I
have
> > > the
> > > reader set to CommandBehavior.CloseConnection.  This would be ok as I
> can
> > > close the DataReader, which should close the connection if I do a:
> > >
> > > dbReader = RunProcedure(...)
> > > dbReader.Close()
> > >
> > > But how do I deal with (or can I) the situation where I do a direct
> > > Databind
> > > to Grid, listbox, etc?
> > >
> > > DataGrid1.DataSource = RunProcedure()
> > >
> > > I have no DataReader to close.
> > >
> > > Thanks,
> > >
> > > Tom
> > >
> > >
> >
> >
>
>

"tshad" <t**@dslextreme.com> wrote in message
news:OUpdvS3FGHA.312@TK2MSFTNGP09.phx.gbl...
> "tshad" <t**@dslextreme.com> wrote in message
> news:Ob6ZxjzFGHA.3984@TK2MSFTNGP14.phx.gbl...
>> "William (Bill) Vaughn" <billvaRemoveT***@nwlink.com> wrote in message
>> news:OdfK7etFGHA.3984@TK2MSFTNGP14.phx.gbl...
>> > Complex bound controls (those that deal with the entire rowset)
>> > automatically close the DataSource when they complete population. This
>> means
>> > you don't have to close a DataReader when binding it to a Grid or List.
>> > However, this assumes that you've set the
> CommandBehavior.CloseConnection
>> on
>> > the ExecuteReader.
>>
>
> This includes datagrid, datalist, repeater, dropdownlist and listbox?
>
> So if I do (where RunProcedure returns a DataReader and sets
> CommandBehavior.CloseConnection):
>
> DataGrid1.DataSource  = RunProcedure(...)
> DataGrid1.DataBind()
>
> or
>
> theListBox.DataSource =
> objCmd.ExecuteReader(CommandBehavior,CloseConnection)
> theListBox.DataBind()
>
> or
>
> Dim dbReader as SqlDataReader
> ...
> dbReader = objCmd.ExecuteReader(CommandBehavior,CloseConnection)
> while dbReader.Read()
> ...
> end while
>
> I don't have to explicitly close either the Reader or the Connection?
>
> Just want to make sure.
>
> Also, does CommandBehavior,CloseConnection only apply to DataReaders and
> not
> DataAdapters ?
>
> Thanks,
>
> Tom
>>
>> >
>> > hth
>> >
>> > --
>> > ____________________________________
>> > William (Bill) Vaughn
>> > Author, Mentor, Consultant
>> > Microsoft MVP
>> > INETA Speaker
>> > www.betav.com/blog/billva
>> > www.betav.com
>> > Please reply only to the newsgroup so that others can benefit.
>> > This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> > __________________________________
>> >
>> > "tshad" <t**@dslextreme.com> wrote in message
>> > news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
>> > >I have been misunderstanding the closing of the connection.
>> > >
>> > > If I have set CommandBehavior.CloseConnection, I thought that
> connection
>> > > would be closed when you had read through the dataread.  As a matter
> of
>> > > fact
>> > > I found that if I had it set, I couldn't seem to get to the next
>> results,
>> > > if
>> > > there were multiple results (NextResult() would give me an error).
>> > >
>> > > Now I find that I need to close the Reader to close the connection.
>> > >
>> > > This is a problem with my Database object.  I have an object
>> > > (RunProcedure)
>> > > that executes a stored procedure and then returns a DataReader.  I
> have
>> > > the
>> > > reader set to CommandBehavior.CloseConnection.  This would be ok as I
>> can
>> > > close the DataReader, which should close the connection if I do a:
>> > >
>> > > dbReader = RunProcedure(...)
>> > > dbReader.Close()
>> > >
>> > > But how do I deal with (or can I) the situation where I do a direct
>> > > Databind
>> > > to Grid, listbox, etc?
>> > >
>> > > DataGrid1.DataSource = RunProcedure()
>> > >
>> > > I have no DataReader to close.
>> > >
>> > > Thanks,
>> > >
>> > > Tom
>> > >
>> > >
>> >
>> >
>>
>>
>
>

>
> hth
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
>
> "tshad" <t**@dslextreme.com> wrote in message
> news:OUpdvS3FGHA.312@TK2MSFTNGP09.phx.gbl...
> > "tshad" <t**@dslextreme.com> wrote in message
> > news:Ob6ZxjzFGHA.3984@TK2MSFTNGP14.phx.gbl...
> >> "William (Bill) Vaughn" <billvaRemoveT***@nwlink.com> wrote in message
> >> news:OdfK7etFGHA.3984@TK2MSFTNGP14.phx.gbl...
> >> > Complex bound controls (those that deal with the entire rowset)
> >> > automatically close the DataSource when they complete population.
This
> >> means
> >> > you don't have to close a DataReader when binding it to a Grid or
List.
> >> > However, this assumes that you've set the
> > CommandBehavior.CloseConnection
> >> on
> >> > the ExecuteReader.
> >>
> >
> > This includes datagrid, datalist, repeater, dropdownlist and listbox?
> >
> > So if I do (where RunProcedure returns a DataReader and sets
> > CommandBehavior.CloseConnection):
> >
> > DataGrid1.DataSource  = RunProcedure(...)
> > DataGrid1.DataBind()
> >
> > or
> >
> > theListBox.DataSource =
> > objCmd.ExecuteReader(CommandBehavior,CloseConnection)
> > theListBox.DataBind()
> >
> > or
> >
> > Dim dbReader as SqlDataReader
> > ...
> > dbReader = objCmd.ExecuteReader(CommandBehavior,CloseConnection)
> > while dbReader.Read()
> > ...
> > end while
> >
> > I don't have to explicitly close either the Reader or the Connection?
> >
> > Just want to make sure.
> >
> > Also, does CommandBehavior,CloseConnection only apply to DataReaders and
> > not
> > DataAdapters ?
> >
> > Thanks,
> >
> > Tom
> >>
> >> >
> >> > hth
> >> >
> >> > --
> >> > ____________________________________
> >> > William (Bill) Vaughn
> >> > Author, Mentor, Consultant
> >> > Microsoft MVP
> >> > INETA Speaker
> >> > www.betav.com/blog/billva
> >> > www.betav.com
> >> > Please reply only to the newsgroup so that others can benefit.
> >> > This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> > __________________________________
> >> >
> >> > "tshad" <t**@dslextreme.com> wrote in message
> >> > news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
> >> > >I have been misunderstanding the closing of the connection.
> >> > >
> >> > > If I have set CommandBehavior.CloseConnection, I thought that
> > connection
> >> > > would be closed when you had read through the dataread.  As a
matter
> > of
> >> > > fact
> >> > > I found that if I had it set, I couldn't seem to get to the next
> >> results,
> >> > > if
> >> > > there were multiple results (NextResult() would give me an error).
> >> > >
> >> > > Now I find that I need to close the Reader to close the connection.
> >> > >
> >> > > This is a problem with my Database object.  I have an object
> >> > > (RunProcedure)
> >> > > that executes a stored procedure and then returns a DataReader.  I
> > have
> >> > > the
> >> > > reader set to CommandBehavior.CloseConnection.  This would be ok as
I
> >> can
> >> > > close the DataReader, which should close the connection if I do a:
> >> > >
> >> > > dbReader = RunProcedure(...)
> >> > > dbReader.Close()
> >> > >
> >> > > But how do I deal with (or can I) the situation where I do a direct
> >> > > Databind
> >> > > to Grid, listbox, etc?
> >> > >
> >> > > DataGrid1.DataSource = RunProcedure()
> >> > >
> >> > > I have no DataReader to close.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Tom
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

"tshad" <t**@dslextreme.com> wrote in message
news:udnPtEEGGHA.1288@TK2MSFTNGP09.phx.gbl...
> "William (Bill) Vaughn" <billvaRemoveT***@nwlink.com> wrote in message
> news:%23E1f4X5FGHA.1192@TK2MSFTNGP11.phx.gbl...
>> The responsibility of any complex bound control (those that display an
>> entire rowset) is to close the DataReader post population.
>> The DataAdapter is not bindable. However, the DataTable within the
> generated
>> DataSet is. In this case the DataAdpater has already executed the Fill
>> method (which opens a DataReader) to populate the DataTable(s) and if
>> (and
>> only if) the Connection was closed when the Fill is executed, the
> Connection
>> will be closed when rowset population is complete.
>
> What about the ListBox, which is also Bindable?  Would I need to close
> that
> connection or would the Listbox close it for me?
>
> theListBox.DataSource =
> objCmd.ExecuteReader(CommandBehavior,CloseConnection)
> theListBox.DataBind()
>
> Also, what about this case, (RunProcedure returns a DataReader that sets
> CommandBehavior.CloseConnection):
>
> Dim dbReaderAs SqlDataReader
> for each oItem as DataGridItem in DataGrid1.items
>    dbReader = myDbObject.RunProcedure("DeleteEmailMessageSent",
> parameters,rowsAffected)
> Next
>
> Would I need to put a close after each execution of RunProcedure ( I
> assume
> this would be the case), or could I put it after the Next command (only
> close it once).  If this were to run 5 loops, would it use 5 different
> connections (if so, I would assume that I would need to close each
> connection (before the Next statement).
>
> Also, if I were to do the following, (assuming RunProcedure passes back a
> DataReader that has set CommandBehavior.CloseConnection)
>
> Dim dbReader As SqlDataReader
> ...
> dbReader = RunProcedure ()
> DataGrid1.DataSource  = dbReader
> DataGrid1.DataBind()
> dbReader.Close()
>
> If the DataGrid1 would close the dbReader (and therefore the connection in
> this case because of the CommandBehavior), would the dbReader.Close()
> cause
> an error trying to close a connection that has already been closed or
> would
> it know that it had been closed and just return with no error?
>
> Thanks,
>
> Tom
>
>>
>> hth
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> __________________________________
>>
>> "tshad" <t**@dslextreme.com> wrote in message
>> news:OUpdvS3FGHA.312@TK2MSFTNGP09.phx.gbl...
>> > "tshad" <t**@dslextreme.com> wrote in message
>> > news:Ob6ZxjzFGHA.3984@TK2MSFTNGP14.phx.gbl...
>> >> "William (Bill) Vaughn" <billvaRemoveT***@nwlink.com> wrote in message
>> >> news:OdfK7etFGHA.3984@TK2MSFTNGP14.phx.gbl...
>> >> > Complex bound controls (those that deal with the entire rowset)
>> >> > automatically close the DataSource when they complete population.
> This
>> >> means
>> >> > you don't have to close a DataReader when binding it to a Grid or
> List.
>> >> > However, this assumes that you've set the
>> > CommandBehavior.CloseConnection
>> >> on
>> >> > the ExecuteReader.
>> >>
>> >
>> > This includes datagrid, datalist, repeater, dropdownlist and listbox?
>> >
>> > So if I do (where RunProcedure returns a DataReader and sets
>> > CommandBehavior.CloseConnection):
>> >
>> > DataGrid1.DataSource  = RunProcedure(...)
>> > DataGrid1.DataBind()
>> >
>> > or
>> >
>> > theListBox.DataSource =
>> > objCmd.ExecuteReader(CommandBehavior,CloseConnection)
>> > theListBox.DataBind()
>> >
>> > or
>> >
>> > Dim dbReader as SqlDataReader
>> > ...
>> > dbReader = objCmd.ExecuteReader(CommandBehavior,CloseConnection)
>> > while dbReader.Read()
>> > ...
>> > end while
>> >
>> > I don't have to explicitly close either the Reader or the Connection?
>> >
>> > Just want to make sure.
>> >
>> > Also, does CommandBehavior,CloseConnection only apply to DataReaders
>> > and
>> > not
>> > DataAdapters ?
>> >
>> > Thanks,
>> >
>> > Tom
>> >>
>> >> >
>> >> > hth
>> >> >
>> >> > --
>> >> > ____________________________________
>> >> > William (Bill) Vaughn
>> >> > Author, Mentor, Consultant
>> >> > Microsoft MVP
>> >> > INETA Speaker
>> >> > www.betav.com/blog/billva
>> >> > www.betav.com
>> >> > Please reply only to the newsgroup so that others can benefit.
>> >> > This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> > __________________________________
>> >> >
>> >> > "tshad" <t**@dslextreme.com> wrote in message
>> >> > news:uzYCSrrFGHA.2896@TK2MSFTNGP10.phx.gbl...
>> >> > >I have been misunderstanding the closing of the connection.
>> >> > >
>> >> > > If I have set CommandBehavior.CloseConnection, I thought that
>> > connection
>> >> > > would be closed when you had read through the dataread.  As a
> matter
>> > of
>> >> > > fact
>> >> > > I found that if I had it set, I couldn't seem to get to the next
>> >> results,
>> >> > > if
>> >> > > there were multiple results (NextResult() would give me an error).
>> >> > >
>> >> > > Now I find that I need to close the Reader to close the
>> >> > > connection.
>> >> > >
>> >> > > This is a problem with my Database object.  I have an object
>> >> > > (RunProcedure)
>> >> > > that executes a stored procedure and then returns a DataReader.  I
>> > have
>> >> > > the
>> >> > > reader set to CommandBehavior.CloseConnection.  This would be ok
>> >> > > as
> I
>> >> can
>> >> > > close the DataReader, which should close the connection if I do a:
>> >> > >
>> >> > > dbReader = RunProcedure(...)
>> >> > > dbReader.Close()
>> >> > >
>> >> > > But how do I deal with (or can I) the situation where I do a
>> >> > > direct
>> >> > > Databind
>> >> > > to Grid, listbox, etc?
>> >> > >
>> >> > > DataGrid1.DataSource = RunProcedure()
>> >> > >
>> >> > > I have no DataReader to close.
>> >> > >
>> >> > > Thanks,
>> >> > >
>> >> > > Tom
>> >> > >
>> >> > >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>