On Friday, September 9, 2016 at 4:11:05 PM UTC-5, GS wrote:
Those dependant DV lists have proven themselves over many years to work
'flawlessly' when properly configured. DV doesn't have the ability to
use filters, thus why your breakout formulas work. Rethink how your
project works and go with proven methods!<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

But I'm not really filtering anything, I'm adjusting the starting row shift & the depth of a single column OFFSET() range. The formulas behind the components of the OFFSET() function return the same integer values, regardless of how the selections are made, so why doesn't the Dynamic Range respond the same way?

I'm just trying to determine whether I've hit a limit of Excel functionality or I've got an error in my formulas/configuration.

My model depends upon asking other people to provide the data in that list (I know what it looks like & how to get it, but I don't have access to extract it myself) and it's likely the data will need to be refreshed a few times before it's finalized. I'd much rather give them a single select statement that they can save in a single results file than a dozen select statements that they have to save into a dozen files.

I understand that code is code & sometimes the arrangements of the 1's & 0's result in something that falls outside of design. Maybe that's where I'm at & I need to request an enhancement (that may or may not ever be incorporated into the product).

However, I don't advocate letting "the way we've always done things" stand in the way of "the way we ought to do things".

If we limit our thinking to "=A1+A2+A3" because it's a tried & true method, we'll never get:
=SUM(A1:A3)
=SUMIF(A1:A3, "0")
and {=SUM((A1:A30)*(A1:A3))}

Again, at present, I'm just trying to assess whether it's a software limit, or a logic/configuration error.

If it's a software limit, then it sounds like I'll have to break the data into separate lists, exactly as you've described. If I've simply not configured something correctly, a single list is more considerate to the folks I have to rely on.