Struggling with blank results when linking golf stats across sheets

There is a particular kind of frustration that lives in a spreadsheet formula that returns a blank when you know the answer is sitting right there. The user in this story built a tidy golf stats workbook, with a "Scores" sheet tracking every round and separate sheets per course, each with dates across row 2 and tee colors waiting to be filled in row 3. The formula logic makes sense on paper: match the course name, match the date, pull the color. But Excel gives them nothing. No error, no warning, just empty cells. The root of the problem is a classic one, and it is worth naming directly: the formula compares entire ranges, not individual values. When you write `Scores!$A$1:$A$2000=$A$2`, Excel does not know you mean "match this one cell against each row." It evaluates that as an array operation, and in a single-cell context, it returns a result that does not do what you expect. The same issue applies to the date comparison and the final range return. The formula is not broken because the data is wrong; it is broken because the approach treats a lookup like a logical test across a whole column. This is a common pain point, and it is the same kind of conceptual leap that appears in other data problems we have covered, like Beyond Similarity Scores: Deduplicating Data with Deterministic Stages, where the challenge is about moving from fuzzy intuition to precise, repeatable logic. The practical fix here is to stop using an array formula and instead use a lookup function that handles the matching for you. Something like `INDEX` combined with `MATCH`, or a simple `SUMPRODUCT`, or even `XLOOKUP` with a concatenated key, would solve this cleanly. For example, you could create a helper column in the "Scores" sheet that combines course name and date, then use that as the lookup value. Or, if you want to stay closer to the original structure, use `SUMPRODUCT` to return the value from column BC where both conditions are true. The user is not far off; they just need to shift from thinking in terms of "if this whole range matches" to "find the row where this specific value exists." What is worth reflecting on here is not just the specific formula, but what it represents. This user is doing something smart: they are trying to build a structured, self-maintaining workbook for a personal passion project. They have separate sheets per course, a central log, and a clear goal for how data should flow. That is good design. The barrier is not their understanding of golf or even of spreadsheets; it is the gap between how we talk about data in our heads and how Excel actually evaluates it. That same gap shows up in other contexts, like Excel not filtering unique values, where users are often surprised that a feature behaves differently than they expect because of hidden characters or inconsistent data types. The lesson is always the same: check your assumptions, test small, and understand the difference between what you intend and what the tool interprets. If a reader came to us with this exact problem, our first question would be simple: have you tried using `INDEX` and `MATCH` together? Because once you stop treating the formula as a one-liner that should just work, and instead break it into its component parts, the solution becomes obvious. You need to find the row number where both conditions are true, and then pull the value from that row in column BC. That is a two-step process, and trying to force it into a single `IF` statement is what caused the blank result in the first place. The takeaway here is not that Excel is difficult; it is that precision matters. You cannot assume that because a formula looks logical, it will behave logically. You have to verify each step, and when something returns blank, ask not "why is there no data" but "what is this function actually evaluating?