Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Exit For at the parent level
Message
De
18/03/2015 16:10:27
 
 
À
18/03/2015 15:55:00
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Versions des environnements
Environment:
VB 9.0
OS:
Windows 8.1
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01616929
Message ID:
01616945
Vues:
33
>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
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform