I received the error message
"Excel ran out of resources while attempting to calculate one or more formulas"
on **ONE** of my computers (Out of 2).

My worksheet contains: (Inside a single worksheet, not workbook, there are formulas in another worksheet)

- > 1,000,000 formulas
- a Pivot table base on 900,000 rows of data

When I run excel/vba on the action "Calculate Sheet" (The current worksheet only), the program would pop the following error message:

```
Excel ran out of resources while attempting to calculate one or more formulas
```

on neither I "refresh" a pivot table in (Excel or VBA) or "Calculate Sheet" in (Excel or VBA)

I have 2 computers:

both running 64 bits Windows 7,

both running Excel 2007 32Bit,

I run Excel right after starting Windows,

my development PC with 2GB RAM can run without problem,

another PC with 6GB RAM shown the

`ran out of resources`

error messageRunning on same set of data, same excel file

I also notice that on my development PC, it is using ~ 1.2G RAM, and the non-working PC, it is using 900M RAM prior to clicking the "Refresh"/"Calculate" Action.

**EDIT**

The Non-working Computer can handle data within 100,000 rows of data

**My questions:**

- Why it is working for the computer with less memory but not the one with more memory? (main question)
- What can I do to reduce the memory used by Excel? (sub question) (Other than deleting data)

Any help is appreciated, please point me into the right direction or simply give some clue.

**EDIT**:I am thinking of removing the formulas, and move the logic into vba, and do it by caching the data maybe per 10,000 rows. But this won't solve my problem if "refresh" pivot table would show the same error.

moreRAM. Can you verify there is enough memory free (both physical and swap) on the computer that errors out? Other than that I would say to optimize or split the sheet if possible. 1M formulas sounds a bit big for an Excel sheet? – lc. Jan 2 '13 at 10:07`shell`

and then import the already-calculated data / do minimal clean-up work. 2) LOTS of playing around with my code to try and make it more efficient / less-memory-consumptive... Good luck!!! – John Bustos Jan 2 '13 at 13:48