The Problem (Q-score 4, ranked #292nd of 303 in the Excel VBA archive)
The scenario as originally posted in 2014
I got two columns of data;
A:
12/31/2013
12/30/2013
12/29/2013
12/28/2013
12/27/2013
12/26/2012
B:
10
10
10
10
10
5
my formula is : =SUM(IF(YEAR(G6:G11)=2013,H6:H11,0),0)
in the wizard the answer is 50
but when I hit enter, it displays 55 on the page.
Any thoughts?
SOLUTION:
While writing formula, press “ctrl + shift + enter”
Thank you
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — niche answer (below median) (+7)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.
I believe that you are not entering the formula as an array formula. @Alexandru is right with his comment, in that only the first cell in the range provided is being computed, so that you have YEAR(G2)=2013, which is true, and you get the sum of the whole range H6:H11.
Some workarounds:
-
You array enter the formula. This will require you to press and hold Ctrl+Shift and then press Enter.
-
Use a formula that automatically considers the input as array, such as
SUMPRODUCT:=SUMPRODUCT((YEAR(G6:G11)=2013)*H6:H11) -
Change your logic for this sum and use
SUMIFS, by using the first and last dates of the year as boundaries:=SUMIFS(H6:H11,G6:G11,">=01-Jan-2013",G6:G11,"<=31-Dec-2013")
When to Use It — classic (2013–2016)
Ranked #292nd in its category — specialized fit
This pattern sits in the 98% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.
What changed between 2014 and 2026
The answer is 12 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.