Using the BackgroundWorke r and a SqlDataReader

[Matthias S.]

Hi,

I've written a simple app which should just fetch some data from a
database and render the results into a ListView.

In order to not freeze the GUI, I'm using a BackgroundWorke r. The
arguments for the RunWorkerAsync are the Query to be executed and the
Connectionstrin g. As a result I hoped I could return a SqlDataReader.

The problem is, if I create the SqlDataReader within the
BackgroundWorke r Thread, I can't access it after the Thread has exitted.
If I would create it on the Form (thus within the Forms Thread) and pass
it as an argument to the Thread, I might end up with the risk of two
Threads accessing the same resource (a Forms Property in this case) and
that doesn't sound a nice thing to do.

How can I pass the resulting SqlDataReader from the Thread back to the form?

Any help is greatly appreceated and thanks in advance!

Matthias

[Nicholas Paldino [.NET/C# MVP]]

Matthias,

Can you show an example of how you are using the BackgroundWorke r class?
AFAIK, you shouldn't have an issue if you create a SqlDataReader and pass it
around (the OleDb provider I can understand, but not the SqlProvider).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Matthias S." <po*****@emvoid SPAMTRAP.de> wrote in message
news:uB******** ******@TK2MSFTN GP09.phx.gbl...

Hi,

I've written a simple app which should just fetch some data from a
database and render the results into a ListView.

In order to not freeze the GUI, I'm using a BackgroundWorke r. The
arguments for the RunWorkerAsync are the Query to be executed and the
Connectionstrin g. As a result I hoped I could return a SqlDataReader.

The problem is, if I create the SqlDataReader within the BackgroundWorke r
Thread, I can't access it after the Thread has exitted. If I would create
it on the Form (thus within the Forms Thread) and pass it as an argument
to the Thread, I might end up with the risk of two Threads accessing the
same resource (a Forms Property in this case) and that doesn't sound a
nice thing to do.

How can I pass the resulting SqlDataReader from the Thread back to the
form?

Any help is greatly appreceated and thanks in advance!

Matthias

[Matthias S.]

Hi Nicholas,

I'm trying to copy/paste the most relevant parts. All ErrorHandling has
been removed. Basically, we need to know only the two EventSinks for the
following BackgroundWorke r events:

- DoWork
- RunWorkerComple ted
This is the EventSink for the DoWork event:

private void OnWorkerStart(o bject sender, DoWorkEventArgs args) {

// the DBWorkerArgs contain two public fields which are
// quite selfexplanatory : ConnectionStrin g and Query
DBWorkerArgs workerArgs = (DBWorkerArgs) args.Argument;

// open connection
SqlConnection con = new SqlConnection(w orkerArgs.Conne ctionString);

con.Open();

// run the query again, checks on the SqlConnection ommitted...
SqlCommand cmd = new SqlCommand(work erArgs.Query, con);
SqlDataReader reader = cmd.ExecuteRead er();

// to make the Results available in the
// BackgroundWorke r.RunWorkerComp leted event, we put them
// into the args.Result

args.Result = reader;

con.Close();

// done...
}

This is the EventSink for the RunWorkerComple ted event:

private void OnWorkerComplet ed(object sender,
RunWorkerComple tedEventArgs args) {

// typechecking omitted
SqlDataReader reader = (SqlDataReader) args.Result;

// _ResultList is a ListView Control on the Form
_ResultList.Ite ms.Clear();
_ResultList.Col umns.Clear();

// columns first
int nFieldCt = reader.FieldCou nt;

for (int i = 0; i < nFieldCt; i++) {
_ResultList.Col umns.Add(reader .GetName(i), 100);
}
}

Both methods are located withing Form1.

Thanks already for looking into my issue :)

Matthias

Nicholas Paldino [.NET/C# MVP] wrote:

Matthias,

Can you show an example of how you are using the BackgroundWorke r class?
AFAIK, you shouldn't have an issue if you create a SqlDataReader and pass it
around (the OleDb provider I can understand, but not the SqlProvider).