Why is DoEvents bad?

I've seen on these boards a lot that people have been criticized for using DoEvents in a loop. Why is this bad? To me it sounds like a good idea to give control back to Windows temporarily to let it catch up on what it needs to do.

Also, I have a loop in one of my programs that updates a progress bar. Well the progress bar won't graphically show the updates unless I have a doEvents statement in there.
Is there another way to get it to graphically update?

Many thanks!

Doevents actually only concerns your program not any others. The bad thing about doevents is that it hangs up your app if called after all forms are unloaded.

Doevents updates the graph? yeah that because a WM_Paint message is queing for being processed by your app :)
Well a good way to avoid probs with doevents is to check if there are any forms left.

Code:

---

'for a loop
Do while forms.count
doevents
'code
loop
'and another one
Do
'code
doevents
Loop while forms.count
'and other frequently used code
If forms.count then doevents

---

It's kinda bad to use doevents to redraw the progress bar, this code is faster:

Code:

---

ProgressBar.Refresh

---

The code is faster then doevents, because doevents gives every program a chance to do something.

Not really, doevents gives only your program a chance to handle it's message queue, that's if the progressbar is the only thing to update, then it will update without any other process being executed

thanks a bunch guys