Let's dive into the weeds of the mappings formula discussed in my earlier posts. Our goal is to translate fields without any hardcoded string literals or direct references to the fields. By dereferencing formulas, we make them adaptable to change and easy to copy/paste formulas without changing the references. First let's review the following mappings formula: This formula uses the header to "map" another field in its row to a mapped value. The from=>to mappings are defined in the "Mappings" tab. The first inner "Index" function gets the value in the "neighborhood" column. This is in LOC 4 and 7 (used to return the default value). Here is the syntax highlighting from that LOC: "MappingsHeaders" is a named range set to the first row of the "Mappings" tab. The second inner "Index" returns the mapped-from range. This is what the offset in the original formula returned. Here's the "ne...
Charles Williams of FastExcel put together a survey asking his visitors to tag the best and worst functions in Excel. Indirect and Offset are high on that list which makes me question my first post's mapping formula; Indirect even got its own Excel's Most Evil Function post! This post fixes my dynamic mapping formula by using hero functions and then looks at the readability and performance differences. The original "SuperNeighborhood" formula was: The new "FastSuperNeighborhood" formula is: I prototyped diagnostic VBA code to calculate the columns and return the execution time. The code sets the application to xlCalculationManual and then calculates the selected cells ten times to get a more consistent response. The new, non-indirect code clocked in at 35ms versus 75ms for the old code. I was kind of surprised to see that because the old code only uses the cells that it needs, whereas the new code is a little more lax re its coverage. However indir...