Just a quick FYI - a number of other folks here (particularly Ed Robinson) got very involved in your issue - trying to figure out what it could be. I'm just the lucky one who posted first. <g>

That's great news.

Before we go further, let's take a step back (it's been a while, and my memory ain't what it used to be). You have a form up, and while it's being used for entry, you need to run two different database queries so that you can grab some data, then you want to let the user know when they're done. Do I have it right?

So, if, for instance, you could run the query without other forms, that would be ok? Or do you need those particular forms?

I guess what I'm asking is can you give me the business issue you're trying to solve so that we can work on a correct architecture?

Thanks. Have a great weekend.

yag

>Good news! :) Monday and Tuesday the program ran with no slow down occurring, no performance issues, no loss of Tab functionality, no glitches, no problems, even the not responding problem when the ENTER key is pressed on a check box is not reproducing. I can't believe those two forms caused all those problems, but apparently they did. Anyway, I have to plug them back in, which leads me to a few questions. Is it proper programming procedure to have forms running in the background, that query the database based on a time interval and will become visible to notify the user when results are returned? If so, what is a logical time interval for checking the database so as not to over work the server? Also, should I run the forms on a separate thread and what effect will that have? I assume the forms have to be put in class to be ran on separate thread. Is the code below correct?
>
>objWarningForms = New clsWarningForms()
>Dim Thread1 As New System.Threading.Thread(AddressOf _
>objWarningForms.LoadWarningForms)
>
>Thread1.Start() ' Start the new thread.
>
>Thank you very much for the help and your hard work YAG! It is greatly appreciated.