For control variable already in use vba ошибка

Добрый день, уважаемые форумчане.
Получил в наследство на новом рабочем месте «почти готовый файл». Он, конечно, многое решает в работе. Но есть, по крайней мере, один косяк. Коллега посоветовал к Вам обратиться.
Одна из форм никак открывается. Я пробовал её подогнать по образцу других форм, но не смог. А в работе она совсем не лишняя.
Вот, пришёл к Вам за помощью.
В приложенном примере при запуске формы с кнопки появляется окно

Compile error:
For control variable already in use                             А в коде формы выделяется For i = 2 To

Причём во вроде бы аналогичной нормальной, рабочей форме (которую я удалил в примере) такой же фрагмент используется и вроде комбобокс точно такой же, и она работает.
А та, что оставлена в примере, не работает.
Знатоки, пожалуйста, помогите запустить форму.

This particular use of a nested «For» is something that I did not expect. I have trimmed it down to a very simple example. The outer For loop works perfectly using the member of the Type «abc», but the enclosed For statement produces the compiler error. I’ve hunted for an explanation, but so far have found none.

Option Explicit

Private Type abc
    i As Integer
    j As Integer
End Type

Private Sub CommandButton1_Click()
    Dim dog As abc
    Dim cat As abc
    
    For dog.i = 1 To 10
        For cat.i = 5 To 9
        
        Next
    Next
End Sub

asked Jan 23, 2021 at 20:20

Rod's user avatar

According to this documentation, nested for loops must use different variables for their control counter. And according to this documentation, Type elements follow the same rules as variables.

Element names also follow standard variable naming conventions, except that keywords can
be used.

I suppose there must be something about the struct (Type) that when you reference one of its elements, it uses that as a named variable of sorts. So because your two control abcs have an element named i, the for loop is saying «hey, there is already another for loop above me using a control variable named i«. Notice you won’t get the same issue if you use dog.i for the outer loop, and cat.j for the inner.

As for solutions to this, you could store the values of dog.i and cat.i into a separate variable to use with this loop structure:

Private Sub CommandButton1_Click()
    Dim dog As abc
    Dim cat As abc
    Dim x As Integer
    Dim y As Integer
    
    x = dog.i
    y = cat.i
    
    For x = 1 To 10
        For y = 5 To 9

        Next
    Next
End Sub

answered Jan 23, 2021 at 20:37

ArcherBird's user avatar

ArcherBirdArcherBird

2,01910 silver badges35 bronze badges

I had wanted to determine if the error I was seeing was a VBA limitation (flaw) or whether there was some Setting or Option that I did not know, that would be appropriate.
I have come up with a work-around that is acceptable for what I need to do.

Option Explicit

Private Type abc1
    i As Byte
    j As Byte
End Type

Private Type abc2
    i As Byte
    j As Byte
End Type

Private Sub CommandButton1_Click()
    Dim dog As abc1
    Dim cat As abc2
    
    For dog.i = 1 To 10
        For cat.i = 5 To 9
        
        Next
    Next
End Sub

answered Jan 24, 2021 at 18:11

Rod's user avatar

Permalink

Cannot retrieve contributors at this time

title keywords f1_keywords ms.prod ms.assetid ms.date ms.localizationpriority

For control variable already in use

vblr6.chm1011174

vblr6.chm1011174

office

9b817917-5156-7dc6-f4f1-4fc6626ad5c9

06/08/2017

medium

When you nest For…Next loops, you must use different control variables in each one. This error has the following cause and solution:

  • An inner For loop uses the same counter as an enclosing For loop. Check nested loops for repetition. For example, if the outer loop uses For Count = 1 To 25, the inner loops can’t use Count as the control variables.

For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).

[!includeSupport and feedback]

  • #1

Greetings,

I am receiving the compile error «For Control Variable Already in Use».

I have nested For Each Next loops with the Control Variable as «Row». I am looping by the row with a predefined range of rows. How can I maintain the nested loop structure and use a variable that loops using a row without using the «For Each Row in CC» structure?

Thanks!

How can you turn a range sideways?

Copy the range. Select a blank cell. Right-click, Paste Special, then choose Transpose.

  • #3

How can I maintain the nested loop structure and use a variable that loops using a row without using the «For Each Row in CC» structure?

Presumably, you wrote something of the form:

Rich (BB code):

For Each row In CC
    For Each row In CC
        [....]
    Next row
Next row

In that context, «row» is a variable name. And by the way, «row» is a poor name to use for a variable because it is also a keyword — a special VBA word like «if», «for», «next», etc.

(VBA can usually tell the difference by context. But it is still considered «poor programming practice».)

Choose different control variable names for each nest for-loop. For example:

Rich (BB code):

For Each r1 In CC
     For Each r2 In CC
         [....]
     Next r2
Next r1

(I like brief control variables. But you might prefer row1 and row2 instead of my r1 and r2.)

Note that the order of control variable names in the Next statements is the opposite of the order in the For statements.

In other words, we always loop innermost for-loops first.

Last edited: Nov 26, 2017

  • #4

Thanks for the reply!

Here is the upper portion of the nested loops:

Code:

For Each Row In CC        
        H = Range(Cells(E, "A")).Row
        BB = PA.ws.Range(Cells(G, "A"), Cells(I, "A")).Row
                      
        With PA.ws
              
            For Each Row In BB

Initially I had integer variables in place of «Row», but received an error «variant or object required». When you assign the control variable r1 and r2, what types of variables are these? Range?

  • #5

If CC and BB are ranges any loop control variable you use with them will also be a range and should be declared as such.

  • #6

Will the machine know to step from the G row variable to the I row variable in .Range(Cells(G, «A»), Cells(I, «A»)).Row when

Code:

Set R2 = .Range(Cells(G,"A")).Row

?

  • #7

Why do you have .Row in the below

Code:

BB = PA.ws.Range(Cells(G, "A"), Cells(I, "A"))[COLOR="#FF0000"].Row[/COLOR]

which changes it from a Range to a number when you have it looping through a range below?

and below you are using Set which only applies to an Object(in this case a range) when the .Row again changes the Range to a number.

Code:

Set R2 = .Range(Cells(G,"A")).Row

I think you need to post your full code

  • Home
  • VBForums
  • Visual Basic
  • Visual Basic 6 and Earlier
  • For Control Variable Already In Use !

  1. Oct 10th, 2003, 04:06 PM


    #1

    NotLKH is offline

    Thread Starter


    pathfinder

    NotLKH's Avatar


    For Control Variable Already In Use !

    For a long Time, I’ve known the following raises the error message «For Control Variable Already In Use».

    VB Code:

    1. Private Sub Command1_Click()

    2. Dim M_I_6() As Long

    3. ReDim M_I_6(2)

    4. List1.Clear

    5. For M_I_6(0) = 0 To 1

    6.     For M_I_6(1) = 0 To 1

    7.         For M_I_6(2) = 0 To 1

    8.             List1.AddItem M_I_6(0) & " " & M_I_6(1) & " " & M_I_6(2)

    9.         Next M_I_6(2)

    10.     Next M_I_6(1)

    11. Next M_I_6(0)

    12. End Sub

    I’ve always used either seperate variables, perhaps MyI, MyJ, and MyK when useing Nested Loops in one procedure, or Dimming something like MyI in an iterative call.

    However, I just thought to test the following, and it works, no problem!

    VB Code:

    1. Private Sub Command1_Click()

    2.     Dim M_I_6() As Long

    3.     ReDim M_I_6(2)

    4.     List1.Clear

    5.     Call DO_I2(M_I_6, 0)

    6. End Sub

    7. Private Sub DO_I2(ByRef MyEmmy2() As Long, ByRef MyLev As Long)

    8. If MyLev > 2 Then

    9.     List1.AddItem MyEmmy2(0) & " " & MyEmmy2(1) & " " & MyEmmy2(2)

    10. Else

    11.     For MyEmmy2(MyLev) = 0 To 1

    12.         Call DO_I2(MyEmmy2, MyLev + 1)

    13.     Next MyEmmy2(MyLev)

    14. End If

    15. End Sub

    As you can see, the Array, M_I_6, is a ByRef array as MyEmmy2 in the DO_I2 sub. I’ve always expected it, if I had thought about it before, that it, too would yell back the error message.

    But It Doesn’t!!!

    Not that I’m complaining, Although I wish I knew that a few years ago. But…

    Do any of you have a decent reasoning why it works useing iterative calls, but not when you use the array elements in one procedure?

    -Lou


  2. Oct 10th, 2003, 06:34 PM


    #2

    plenderj is offline


    Retired VBF Adm1nistrator

    plenderj's Avatar


    Its half twelve at night, I’m not feeling 100%, and I’m a bit tired, but I’d hazard a guess that its a scope issue.
    Namely, that within the current scope of the control variable, modifications cannot be made to it by another for loop.

    Microsoft MVP : Visual Developer — Visual Basic [2004-2005]


  3. Oct 10th, 2003, 06:37 PM


    #3

    VB doesn’t really seem to care that a For control points to the same memory, as long as it has a different name. Consider:

    VB Code:

    1. Sub DoDooDah()

    2.     Dim a As Long

    3.     a = 1

    4.     DooBee a, a

    5. End Sub

    6. Private Sub DooBee(ByRef DooDah1 As Long, ByRef DooDah2 As Long)

    7.     For DooDah1 = 0 To 5

    8.         For DooDah2 = 0 To 5

    9.             Debug.Print DooDah1

    10.         Next

    11.     Next

    12. End Sub

    DooDah1 value changes as DooDah2 changes because they point to the same memory. In effect, that is the same as if I had used the same variable name in both Fors.

    I guess a better question is why your first version doesn’t work. The «already in use» is a compile error. That would indicate that when VB compiles the code it checks for duplicate For controls and doesn’t allow them—not because they wouldn’t really work, but because it thinks you’re a bonehead that forgot that you already used the control in another For (which is probably usually the case).


  4. Oct 10th, 2003, 09:15 PM


    #4

    NotLKH is offline

    Thread Starter


    pathfinder

    NotLKH's Avatar


    Originally posted by WorkHorse
    ….The «already in use» is a compile error. That would indicate that when VB compiles the code it checks for duplicate For controls and doesn’t allow them—not because they wouldn’t really work, but because it thinks you’re a bonehead that forgot that you already used the control in another For (which is probably usually the case).

    so, on the eve of my birthday, you are saying the cdode that i posted indicates i’m i bonehead/

    forgive me for ther lack of capitals and question marks, but its hard to do when your useing only your middle finger.


  5. Oct 10th, 2003, 09:21 PM


    #5

    NotLKH is offline

    Thread Starter


    pathfinder

    NotLKH's Avatar


    Originally posted by plenderj
    [B]Its half twelve at night, I’m not feeling 100%, and I’m a bit tired, [b]

    HAPPY BIRTHDAY hurrrhip! ‘scuze me!


    Namely, that within the current scope of the control variable, modifications cannot be made to it by another for loop.

    But, isn’t, when you dim an array appropriately, arr(0) is NOT the same variable as arr(1)??and one more, for emphasis?

    -Lou


  6. Oct 10th, 2003, 09:29 PM


    #6

    Originally posted by NotLKH
    But, isn’t, when you dim an array appropriately, arr(0) is NOT the same variable as arr(1)??and one more, for emphasis?

    -Lou [/B]

    Makes sense to me. I think boneheads at MS just coded the compiler to look for any «For » & {variable name before any parenthises}. So if it finds «For arr» and another «For arr» without a closing «Next» then raise compile error. I think it is just a text-based check that MS built into the compile builder without thinking any boneheads like you (Happy Bday!!!) would actually use array elements as For controls. (Actually I think they thought people might use arrays, but figured the elements called in the array if variable could cause duplication errors that could lead to problems—endless loops and such. Anyway, I think it’s just a VB compile text checking error that is trying to do the right thing, but doesn’t really work for people that know what they are doing and REALLY do want to use the same variable names for Fors)

    Last edited by WorkHorse; Oct 10th, 2003 at 09:36 PM.


  • Home
  • VBForums
  • Visual Basic
  • Visual Basic 6 and Earlier
  • For Control Variable Already In Use !


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
  • BB code is On
  • Smilies are On
  • [IMG] code is On
  • [VIDEO] code is On
  • HTML code is Off

Forum Rules


Click Here to Expand Forum to Full Width

Понравилась статья? Поделить с друзьями:
  • Fopen код ошибки
  • Foobar cue ошибка
  • Font capture acrord32 exe ошибка приложения
  • Fondital ошибка е51
  • Fondital ошибка e02