VBA Alternative for xlPasteValues?

Thank you, RomperStomper. Based on your reply I reviewed my testing more carefully and found that the values from the formulas were being pasted back to the original cells while the target cells were being ignored. I am still doing more testing before replying with changed code and the results I am getting.

Thanks for your input. I am sure you are right. I am still working on code that will move the values from the source workbook to a different target workbook without changing the formulas in the source workbook.

I want to thank romperstomper and JBeaucaire for their contributions and help.

I am attaching a simple spreadsheet with a solution macro included.

I also learned that the issue of slow execution was due to multiple factors. I will explain so if you are interested in faster coding this may save you a lot of frustration.

Environment:
Dell laptop, Intel T2400 dual processor @ 1.83 Ghz, 0.99GB of Ram, Windows XP, MS Office 2003.

The Goal:
The Workbook that was giving the most trouble was a mini-monster of 233 MB.
It included 3 sheets of raw data (approximately 1000 rows by 250 columns each). It also included several worksheets FULL of cell formulas ( 1010 rows by 251 columns per sheet). This was one of several workbooks in a series that I knew had to be condensed in order to be manageable as there are updates to the raw data every week.

The Approach:
My approach was to update the raw data, then resolve the formulas and save the results to another workbook name. Then I could read the results from this condensed workbook in order to update the next workbook in the series. (When the formulas are resolved into mere values, the workbook only measures 38 MB in size.)

The Problem:
As indicated in the original Posting, the VBA code was taking many hours to process using the Select, Copy, and PasteSpecial technique. Previously on this forum I had learned a number of techniques for speeding up the code. In one instance copying an entire sheet of data (1000 X 250) took only seconds rather than half an hour.

However, when copying values from complex formulas, I still experienced significant time issues when large quantities of cells were involved. I built some time stamps into my code, and experimented with the order in which I converted the various sheets of formulas. In doing so I learned some major lessons. One large sheet of formulas was taking 7 hours to process using the Select, Copy, PasteSpecial method, only took 4 hours when the values were read into an array then read back into the sheet. Furthermore, while it took 4 hours to process when it was the first sheet of formulas to be resolved, it only took one minute when it was the last worksheet to be resolved. Further experiments demonstrated that when the size of the whole workbook had been reduced below 200MB worksheet conversions that had been taking one to four hours were all completing in a minute or less for each sheet.

Conclusion:
Reading (using an "=" statement) a large range into an array then writing the values back into a sheet (essentially reversing the same statement) works significantly faster than looping or even Range based copy and paste instructions. Also, in extremely large workbooks, it is far faster to process through multiple workbooks of under 200 MB than using one large one. ( I currently have five workbooks in a series. The problem workbook starts at 233 MB and takes almost 3 hours to process 500,000 cells followed by 5 minutes to process the remaining 750,000 cells. The remaining workbooks vary in size from 50 MB to 193 MB and only take 15 minutes to process their 4,000,000 cells.)

My next challenge is to restructure the largest workbook so I can break it into at least two smaller workbooks.

Note:
The solution macro included in the attached workbook has a number of code accelerating techniques included.