I agree.
> This is the right way, thanks!
> One question:
> what about ADO.NET postings?
>
> often they are
> - SQL (language&server) problems,
> - OLE DB related
> - or very specific to one of the (new native) data providers!
You can read messages from the DOTNET archive, unsubscribe from
> The problem that this list partioning is designed to solve (excessive list
> volume) would be fixed if we could wave a magic wand and eliminate all off-
> topic or personal posts.
To a degree yes, but there are also quite a few on-topic threads that I'm not
interested in at the moment that I mu
w and manipulate as necessary, then save the data back to the
database. If you had no database then of course you'd have no data to fill the
dataset with nor would you have a place to store changes.
Greg Ward
www.VB-FAQ.com
VB Developer's FAQ site
*
you are also reducing load on that
server.
Greg Ward
www.VB-FAQ.com
VB Developer's FAQ site
> -Original Message-
> From: The DOTNET list will be retired 7/1/02
> [mailto:[EMAIL PROTECTED]]On Behal
Blain,
I believe that the DataReader does not automatically close like a DataAdapter
does.
> -Original Message-
> From: The DOTNET list will be retired 7/1/02
> [mailto:[EMAIL PROTECTED]]On Behalf Of Blain Timberlake
> Sent: Wednesday, June 05, 2002 7:46 AM
> To: [EMAIL PROTECTED]
> Su
No, you said that the error was an open DataReader, not a DataSet.
I'm assuming you use the DataReader to fetch the data and then load the data
into the DataSet. If so then you need to do ...
myDataReader.Close()
> -Original Message-
> From: The DOTNET list will be retired 7/1/02
> [
Weird.
I'm new at this too but that sure seems to contradict what I have read. Maybe
someone else can explain why you'd get an error on an open DataReader even
though none are declared/instantiated.
> -Original Message-
> From: The DOTNET list will be retired 7/1/02
> [mailto:[EMAIL