The Problem (Q-score 45, ranked #5th of 303 in the Excel VBA archive)
The scenario as originally posted in 2013
I would like to write an IF statement, where the cell is left blank if the condition is FALSE.
Note that, if the following formula is entered in C1 (for which the condition is false) for example:
=IF(A1=1,B1,"")
and if C1 is tested for being blank or not using =ISBLANK(C1), this would return FALSE, even if C1 seems to be blank. This means that the =IF(A1=1,B1,"") formula does not technically leave the cells blank if the condition is not met.
Any thoughts as to a way of achieving that? Thanks,
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds elite answer (top 10 %%) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — elite answer (top 10 %%) (+44)
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.
Unfortunately, there is no formula way to result in a truly blank cell, "" is the best formulas can offer.
I dislike ISBLANK because it will not see cells that only have "" as blanks. Instead I prefer COUNTBLANK, which will count "" as blank, so basically =COUNTBLANK(C1)>0 means that C1 is blank or has "".
If you need to remove blank cells in a column, I would recommend filtering on the column for blanks, then selecting the resulting cells and pressing Del. After which you can remove the filter.
When to Use It — classic (2013–2016)
A top-10 Excel VBA pattern — why it still holds up
Ranks #5th of 303 in the Excel VBA archive. The only pattern ranked immediately above it is “Generating CSV file for Excel, how to have a newline inside a…” — compare both if you’re choosing between approaches.
What changed between 2013 and 2026
The answer is 13 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.