Well just for kicks, I have each one of those dataAdapter.fill(....)
statements each using their own connection and I still get the same
problem.

So now none of these guys are sharing a connection, which kind of kills
my first stab at the problem.  Could anyone clue me in as to why I'd
still be getting these DataReader errors?

=Blain

-----Original Message-----
From: The DOTNET list will be retired 7/1/02
[mailto:[EMAIL PROTECTED]] On Behalf Of Greg Ward
Sent: Wednesday, June 05, 2002 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Connection Question

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 PROTECTED]]On Behalf Of Blain Timberlake
> Sent: Wednesday, June 05, 2002 1:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET] Connection Question
>
>
> Well I'm not using a datareader unless it is used internally to a
> SQLDataAdapter which it may very well be.
>
> I do the following:
> daGetRunningParams.Fill(dsRunningParams)
>
> where daGetRunningParams is a DataAdapter that executes an SQL
statement
> to get a table back.  I had just assumed it used a datareader internal
> to that.  Is that not the case?  I have no datareaders explicitly
> declared anywhere.

You can read messages from the DOTNET archive, unsubscribe from DOTNET,
or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to