Excel: ‘Unable to set the Calculation property of the Application class’

calendar_today Asked Nov 9, 2008
thumb_up 6 upvotes
history Updated April 14, 2026

Direct Answer

Googling produces this suggestion: You need to have a open workbook, ie xl.Workbooks.Add xl.Calculation = xlCalculationManual. This is a 3-line Excel VBA snippet, ranked #202nd of 303 by community upvote score, from 2008.


The Problem (Q-score 7, ranked #202nd of 303 in the Excel VBA archive)

The scenario as originally posted in 2008

I’m trying to automate some stuff in MS Excel. When I try to set the Calculation property I get the following error message: ‘Unable to set the Calculation property of the Application class’

I believe this property should be settable.

Any advice appreciated!

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) (+6)

3-line Excel VBA pattern (copy-ready)

Googling produces this suggestion:

You need to have a open workbook, ie

xl.Workbooks.Add
xl.Calculation = xlCalculationManual


When to Use It — vintage (14+ years old, pre-2013)

Ranked #202nd 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 2008 and 2026

The answer is 18 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 +6 vs the Excel VBA archive median ~4; this entry is niche. The score plus 7 supporting upvotes on the question itself (+7) means the asker and 5 subsequent voters all validated the approach.

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

Yes. The 3-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.

This answer is 18 years old. Is it still relevant in 2026?
expand_more

Published 2008, which is 18 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 #201?
expand_more

The pattern one rank above is “What are the differences between using the New keyword and calling CreateObject in Excel VBA?”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 7, Answer-score 6, original post 2008, ranked #202nd of 303 in the Excel VBA archive. Last regenerated April 14, 2026.

excel