Do X until Y or Z ??

[kor]

Is there a way to have a Do loop have an Or statement?

Do x until y or z ?

I have a loop that checks if a user exists in active directory. I want to keep looping until the user does exist, OR 5 minutes has passed. (i dont want the loop sitting there for hours stuck. If the user doesnt exist after 5 minutes skip and move on)

Here is my current code.

#include <AD.au3>

_AD_Open()

$username = "2"

$userexists = ""
Do
$getattribute = _AD_GetObjectAttribute($username, "sAMAccountName")
If _AD_ObjectExists($username, "sAMAccountName") Then
    msgbox(0, '', "exists")
    $userexists = True
ElseIf @error = 1 Then
    msgbox(0, '', "does not exist")
    $userexists = False
Else
    Exit
    ; dont know what to do
EndIf
Until $userexists = True

msgbox(0, '', "end of loop")

_AD_Close()

I want to have an

Until $userexists = True Or XXX

Where XXX is a 5 minute timer

Or what I can do is put a sleep statement in the above loop, for say 30 seconds. then just make the timer have 10 steps. So the loop only runs 10 times. But how can I do that?

Edited January 18, 2011 by kor

[kor]

Thinking out loud. Does this look right?

; Open connection to AD
_AD_Open()

$username = "2"

$userexists = ""
$steps = 0
Do
$getattribute = _AD_GetObjectAttribute($username, "sAMAccountName")
If _AD_ObjectExists($username, "sAMAccountName") Then
    msgbox(0, '', "exists")
    $userexists = True
ElseIf @error = 1 Then
    msgbox(0, '', "does not exist")
    $userexists = False
    $steps = $steps + 1
Else
    Exit
    ; dont know what to do
EndIf
Sleep(300)
Until $userexists = True Or $steps = 10

msgbox(0, '', "end of loop")


; Close connection to AD
_AD_Close()

[MvGulik]

Until $userexists Or $steps > 9

- no need to test if a bool = true, only to get a other bool in its place.

- even if you do use a step value of one(1) ... save coding style is to test for a upper/lower range value case, not just for a specific single value.

[ReaImDown]

Until $userexists Or $steps > 9

- no need to test if a bool = true, only to get a other bool in its place.

- even if you do use a step value of one(1) ... save coding style is to test for a upper/lower range value case, not just for a specific single value.

^100% correct