DoEvents was great to keep a tight process from hogging the system, but in NT 4.0 if you check you'll find your cpu usage going to 100 percent quick.

Try adding a line with Sleep 1 after DoEvents to your tight loops, this will only cost you 1 ms and if you just call the sleep command every 150 or 200 passes, it doesn't cost you much. On my PC the procedure below shows 1% or less change to my cpu usage. If you Rem out the sleep line cpu usage hits 100% quick.

Declare

Private Declare Sub Sleep Lib "Kernel32" (ByVal dwmilliseconds As Long)

Sample Code

Private Sub Command1_Click()

Dim iCounter As Integer

Do

'Your Process

For iCounter = 1 To 10000

DoEvents

' 200 seems like a good value to ensure

' min. slow down with min. load on cpu usage

' according to NT 40's Task Manager

' the next line will cost you t ms for every

' 200 passes

If iCounter Mod 200 = 0 Then

Sleep 1

End If

Next

Loop

End Sub