Forum Discussion

liquidphantom's avatar
liquidphantom
Occasional Contributor
7 years ago

Unable to remove a column from a Table variable

Absolutly stumped on this one.   I have a ProjectSuite table variable that is 0x0 size when the suite starts. In the first test case to use the table I add each required column, 6 in total, then ad...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    When you remove a column, the column count reduces.... so, when you remove column index 0, now the max number of columns is down to 5.... when you remove 1, it's now 4, when you remove column 2, it's now 3... so, when you remove column 3... well, there are only columns 0, 1, and 2 any more... so column 3 is out of bounds.  What I would do, actually, is completely remove the variable and recreate it rather than add/remove columns.  There is a ProjectSuite.Variables.RemoveVariable method that will remove the variable... wrap it in logic to check "If variable exists, remove it" and then ProjectSuite.Variables.AddVariable to add it back in.  

     

    The alternative option is to run your for loop as a "down to"... stepping down from max to 0.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

When you remove a column, the column count reduces.... so, when you remove column index 0, now the max number of columns is down to 5.... when you remove 1, it's now 4, when you remove column 2, it's now 3... so, when you remove column 3... well, there are only columns 0, 1, and 2 any more... so column 3 is out of bounds.  What I would do, actually, is completely remove the variable and recreate it rather than add/remove columns.  There is a ProjectSuite.Variables.RemoveVariable method that will remove the variable... wrap it in logic to check "If variable exists, remove it" and then ProjectSuite.Variables.AddVariable to add it back in.  

 

The alternative option is to run your for loop as a "down to"... stepping down from max to 0.

  • liquidphantom's avatar
    liquidphantom
    Occasional Contributor
    7 years ago
    Marsha_R wrote:

    Is CC actually = 6 after you set it to column count?

     

    Just curious, why bother to clear the table and recreate?  Tables are free, just create a new one for each test.

    6 is the column count the max column index would be 5.

    I need to use the table over a couple of different scripts. Creating it in the script i'd lose the values when the script ends.

     

    tristaanogrewrote:

    When you remove a column, the column count reduces.... so, when you remove column index 0, now the max number of columns is down to 5.... when you remove 1, it's now 4, when you remove column 2, it's now 3... so, when you remove column 3... well, there are only columns 0, 1, and 2 any more... so column 3 is out of bounds.  What I would do, actually, is completely remove the variable and recreate it rather than add/remove columns.  There is a ProjectSuite.Variables.RemoveVariable method that will remove the variable... wrap it in logic to check "If variable exists, remove it" and then ProjectSuite.Variables.AddVariable to add it back in.  

     

    The alternative option is to run your for loop as a "down to"... stepping down from max to 0.

    Thanks, this gave me a nudge in the right direction, this works

    For Col = CC-1 to 0 step -1

    It's weird though that the standard "For x = 0 to n" works fine elsewhere though.

     

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago

      While it may seem weird... it's not.  You are removing columns based upon index.  So, when you remove a column, the index of the remaining columns changes.

       

      FirstColumn has index 0

      SecondColumn has index 1

      ThirdColumn has index 2.

       

      So... you go in and delete FirstColumn.  When that is done...

       

      SecondColumn has index 0

      ThirdColumn has index 1

       

      If I were to go and try and delete ThirdColumn using the index that it had initially (2), I'd get that error that you're experiencing because that index no longer exists... the COLUMN does... but the index for that column has changed.