Diddi, That looks great... but I still don't think that the VB option will work. The reason is that on a regular basis, it will need to be run on just part of the list rather than the full list, a list based o date and/or store location. Simply having a raw number of the dead count of the complete list wont help me with that. Perhaps if I was VB Jedi status like yourself, but unfortunately I am a novice in VB.
Also, I totally agree with you about the data. Unfortunately I wasn't aware of this until I got into it pretty deep. I was told how easy the project would be and how it's just "pulling info from the Exce sheets we already get, and plugging it into this new sheet so it all looks pretty and readily available". The person who told me that however has no clue how things like this work. I don't claim to be a master by any stretch, but he asked me to do this based on a few sheets I did at a prior organization which worked perfectly and very impressively. But it was completely different, as the data was far closer to the end product. This company is fairly new, and their reporting sucks. So the Excel sheet needs to do the bulk of the work, which is what is killing my data capacity. I'm actually pretty sick about it, because what I thought was going to be an amazing looking and working document, is turning into a nightmare which is fast approaching the limits of processing.