Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Exit For at the parent level
Message
From
19/03/2015 03:09:02
 
 
To
18/03/2015 16:10:27
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows 8.1
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01616929
Message ID:
01616954
Views:
38
>>Haven't checked but if you initialize within the inner for-next isn't that out of scope for the outer?
>
>In the following examples, llStop is available within the scope:
>
>
>        Dim llStop As Boolean = False
>
>        ' For each LXSelection for a disabled
>        For Each loObject In oSelectionDisabled
>
>            ' Reset the value
>            llStop = False
>
>            ' Initialization
>            lcField = loObject(1)
>            lnValue = loObject(2)
>
>            ' For each LXSelection which needs to be replaced with a warning
>            For Each loObject2 In oSelectionWarning
>
>                ' Initialization
>                lcField2 = loObject(1)
>
>                ' If this field is a request for a disable and a warning
>                If lcField = lcField2 Then
>
>                    ' We cancel as the warning has priority
>                    llStop = True
>                    Exit For
>
>                End If
>
>            Next
>
>            ' If we stop
>            If llStop Then
>                Continue For
>            End If
>
>            ' Additional code here
>            ...
>
>        Next
>
But declared in the outer scope not the inner
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform