2 ways for “ClearContents” on VBA Excel, but 1 work fine. Why?

calendar_today Asked Sep 23, 2013
thumb_up 8 upvotes
history Updated April 14, 2026

Direct Answer

That is because you are not fully qualifying your cells object. Try this With Worksheets("SheetName") .Range(.Cells(1, 1), .Cells(10, 2)).ClearContents End With Notice the DOT…. This is a 4-line Excel VBA snippet, ranked #246th of 303 by community upvote score, from 2013.


The Problem (Q-score 4, ranked #246th of 303 in the Excel VBA archive)

The scenario as originally posted in 2013

Good evening friends:

I have in mind 2 ways for clearing a content in a defined range of cells of a VBA project (in MS Excel):

  1. Worksheets("SheetName").Range("A1:B10").ClearContents
  2. Worksheets("SheetName").Range(Cells(1, 1), Cells(10, 2)).ClearContents

The problem is that the second way show me an error ‘1004‘ when I’m not watching the current Worksheet “SheetName” (in other words, when I haven’t “SheetName” as ActiveSheet).

The first way work flawlessly in any situation.

Why does this happen? How can I use the “Second way” without this bug?

Why this Range / Worksheet targeting trips people up

The question centers on reaching a specific cell, range, or workbook object. In Excel VBA, this is the #1 source of failures after activation events: every property (.Value, .Formula, .Address) behaves differently depending on whether the parent Workbook is explicit or implicit.


The Verified Solution — niche answer (below median) (+8)

4-line Excel VBA pattern (copy-ready)

That is because you are not fully qualifying your cells object. Try this

With Worksheets("SheetName")
    .Range(.Cells(1, 1), .Cells(10, 2)).ClearContents
End With

Notice the DOT before Cells?


When to Use It — classic (2013–2016)

Ranked #246th 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 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.

help
Frequently Asked Questions

This is a below-median answer — when does it still fit?
expand_more

Answer score +8 vs the Excel VBA archive median ~4; this entry is niche. The score plus 4 supporting upvotes on the question itself (+4) means the asker and 7 subsequent voters all validated the approach.

Does the 4-line snippet run as-is in Office 2026?
expand_more

Yes. The 4-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

Published around 2013 — what’s changed since?
expand_more

Published 2013, which is 13 year(s) before today’s Office 2026 build. The Excel VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Excel VBA pattern ranks just above this one at #245?
expand_more

The pattern one rank above is “Split large Excel/Csv file to multiple files on PHP or Javascript”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 4, Answer-score 8, original post 2013, ranked #246th of 303 in the Excel VBA archive. Last regenerated April 14, 2026.

excel-vba