Databases
StackOverflow2013
Postsdbo
PO#VALUE! errors after setting displayed outline level from VBA
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO#VALUE! errors after setting displayed outline level from VBA
    primarykey
    data
    text
    <p>I have reduced my problem to the following test case:</p> <ol> <li><p>create a new workbook;</p></li> <li><p>enter a constant value, e.g. <code>123</code> into <code>Sheet1!A1</code>;</p></li> <li><p>define a name, e.g. <code>foo</code>, that refers to the formula <code>=CHOOSE(!$A$1, Sheet1!$A$1)</code>;</p></li> <li><p>enter the constant value <code>1</code> into <code>Sheet2!A1</code>;</p></li> <li><p>enter the formula <code>=foo</code> into some other cell on <code>Sheet2</code>, e.g. <code>Sheet2!B1</code>: observe that, as expected, the result is the value that was entered into <code>Sheet1!A1</code> in step 2 above;</p></li> <li><p>create then run a VBA procedure containing the following code:</p> <pre><code>Sheets("Sheet1").Outline.ShowLevels 1 </code></pre></li> </ol> <p>You will notice that the cell from step 5 now contains a <code>#VALUE!</code> error.</p> <p>Moreover, a simple sheet recalculation (whether using the <kbd>F9</kbd> key or the <code>Application.Calculate</code> method) does not resolve the problem: one must instead perform either a <em>full</em> recalculation from VBA (using the <code>Application.CalculateFull</code> method) or else a <em>full rebuild</em> from the interactive UI (using the <kbd>CTRL</kbd>+<kbd>ALT</kbd>+<kbd>SHIFT</kbd>+<kbd>F9</kbd> key combination).</p> <p>Through trial-and-error, I have ascertained that for this condition to arise:</p> <ul> <li><p>the <code>CHOOSE()</code> index argument must involve a relative-sheet cell reference (not constants or absolute-sheet references);</p></li> <li><p>the <code>CHOOSE()</code> value argument that is being indexed must involve a reference to another sheet;</p></li> <li><p>the change of displayed outline level must arise from within a VBA <em>procedure</em> (not from the outline controls in the interactive UI or the VBA Immediate Window); and</p></li> <li><p>the <code>ShowLevels</code> method call (whose arguments are irrelevant) must be applied to a sheet that is referenced amongst any of the value (though not index) arguments to <code>CHOOSE()</code>.</p></li> </ul> <p>What's going on?</p> <p>I would very much like to collapse a worksheet that I am referencing amongst the value arguments to <code>CHOOSE()</code> to its highest outline level without triggering this error, as a full recalculation of my actual workbook (still only a few seconds) is undesirable from a UX standpoint.</p> <p>Suggestions for a workaround (whilst still using a defined name containing the <code>CHOOSE()</code> function together with a relative-sheet index argument) would be most welcome!</p> <p>My platform: Excel 2010 (14.0.6123.5001, 32-bit) on Windows 7 Home Premium (SP1, 64-bit).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USeggyal
    1. USeggyal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO#VALUE! errors after setting displayed outline level from VBA
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO#VALUE! errors after setting displayed outline level from VBA
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO#VALUE! errors after setting displayed outline level from VBA
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFor what it's worth, I am unable to reproduce the issue in Excel 2002 SP3 (10.6871.6870, 32-bit) on Windows 7 Home Premium (SP1, 64-bit).
      singulars
      1. PO#VALUE! errors after setting displayed outline level from VBA
      1. USmwolfe02
    2. CO@mwolfe02, hmm.... I can reproduce on Excel 2010 (14.0.6123.5001, 32 Bit) on XP, SP3
      singulars
      1. PO#VALUE! errors after setting displayed outline level from VBA
      1. USSeanC
    3. CO@SeanCheshire: Good to know. It sounds like a bug that was introduced by MS (likely when going from Excel 2003 to 2007). Which simply begs eggyal's question: is there a workaround? ... And this is the point where I bow out and hope others can assist.
      singulars
      1. PO#VALUE! errors after setting displayed outline level from VBA
      1. USmwolfe02
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload