<div>
This is for BGWs within your app right? You can get all open forms from Application.Open forms and then loop through its controls collection to see if there is any BGW.<br />
<br />
For Each frm In Application.OpenForms<br />
&nbsp; &nbsp; &nbsp;For Each ctrl In frm.Controls<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; If TypeOf(ctrl) Is BackGroundWorker Then<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Dim bgw As BackGroundWorker = Ctype(ctrl, BackGroundWorker)<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; msgbox bgw.Name &amp;&nbsp;&quot;, &quot;&nbsp;&amp; bgw.IsBusy.ToString()<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; End If<br />
&nbsp; &nbsp; &nbsp;Next<br />
Next
</div>


<div>
That sounds like exactly what I need. &nbsp;The only thing that doesn't compile is that Name doesn't seem to be a property of BackgroundWorker?
</div>


<div>
It should be but try without it and see if it finds all the BGWs.
</div>


<div>
Hmmm. &nbsp;For now, I'm just doing a bgw.tostring which should show the object type itself after casting it as a BackgroundWorker. &nbsp;It's not picking it up, but I think that's because the background worker is not part of the form. &nbsp;it's defined within a class which is part of the form. &nbsp;Would that collection be somewhere else?<br />
<br />
I know the rest of my code is working because the first thing the background worker does is add itself to a list and the last thing it does is removes itself from a list. &nbsp;I then iterate through that list. &nbsp;However, that leaves me the queasy feeling that I'll mess up that sequence somewhere.
</div>


<div>
Do you have one instance of the class in the form or multiple instances? You can access that one or collection of BGWs inside that form through the form reference in my code.
</div>


<div>
@WJoeMoore said:<br />

<blockquote>
<i>I know the rest of my code is working because the first thing the background worker does is add itself to a list and the last thing it does is removes itself from a list. &nbsp;I then iterate through that list. &nbsp;However, <b>that leaves me the queasy feeling that I'll mess up that sequence somewhere</b>.</i>
</blockquote>
<br />
To avoid concurrency issues, you need to make sure all access to your list is synchronized.
</div>


<div>
@wdosanjos: &nbsp;Thanks for the comment.<br />
<br />
I suppose the way to take care of that would be to use a 'reportprogress' thread to add the item to the list. &nbsp;Putting the removal on the dispose should take care of threading--right? &nbsp;I don't get a threading exception--but of course that doesn't guarantee that there will never be a problem.<br />
<br />
I'm acknowledging that my 'solution' is not good. &nbsp;My question is: &nbsp;How do I find all background processes that exist within a form class--even if they are not components on the form?
</div>


<div>
'You can't do that' is always disappointing, but when it's correct and documented I can live with it. &nbsp;You also covered some other important points.
</div>


<div>
<div class="content wysiwyg-content">
Question about multiple background workers in VB.<br />
<br />
They may be created by multiple classes. &nbsp;I'm trying to create a function within an appliction that determines which, if any, of the background workers are busy. &nbsp;Of course, I know how to query an individual one if I know it exists, but I want Windows to tell me which ones exist and whether or not they are busy.<br />
<br />
Is there an object that will reveal that information to me?<br />
<br />
Thanks.
</div>
</div>


Question about multiple background workers in VB.

They may be created by multiple classes.  I'm trying to create a function within an appliction that determines which, if any, of the background workers are busy.  Of course, I know how to query an individual one if I know it exists, but I want Windows to tell me which ones exist and whether or not they are busy.

Is there an object that will reveal that information to me?

Thanks.

VB 2008 find all running background workers

Visual Basic .NET (VB.NET) is an object-oriented programming language implemented on the .NET framework, but also supported on other platforms such as Mono and Silverlight. Microsoft launched VB.NET as the successor to the Visual Basic language. Though it is similar in syntax to  Visual Basic pre-2002, it is not the same technology,