View Single Post
  #4   Report Post  
Ronald R. Dodge, Jr.
 
Posts: n/a
Default

Corruption could be the reason, but what had me think of the Undo levels is
cause of the large range of data that's being copied, and even at one point,
he states, Range A1:AO1300, though indirectly as it may be. Regardless if
it's being copied from or pasted to, with the default number of undo levels
within Excel being 16, that's a lot of cells to have to be stored into RAM
for a lot of steps.

One thing that was failed to be stated is which version of Excel is being
used. Excel 97, I would not even deal with it cause of how unstable that
version is. That version is so unstable, I would rather work with Lotus
123, v2.3 than to work with Excel 97. It's only Excel 2000 and beyond that
has been truly stablized.

"Dave Peterson" wrote in message
...
I'd do a little experiment.

Create a new workbook and copy over that data (essentially recreating the
workbook).

Then test it out there.

My bet is that your workbook (or worksheet) is corrupted. (You may be
able to
just recreate that worksheet and save yourself some work.)

If you can find someone with a newer version of excel, you may want to try
the
same thing in that version. Each version of excel seems to handle
corruption
better (sometimes just differently, though).

In fact, opening the workbook in OpenOffice and saving (a copy??) there
may be
able to help.

http://www.openoffice.org, a 60-65 meg download or a CD

James wrote:

I have a user who has a excel spreadsheet 0.5Mb. What they are trying
to do
is copy & paste cells columns A to F (rows 1 to 1300) to G to L (rows 1
to
1300) . This copies fine, there are no filters, however there is a bit
of
formula but noting unusually out of the ordinary. So once the data has
copied over they select save and get the following error message;
"Excel.exe has generated errors and will be closed by windows. You will
need to restart the program. An error log is being generated."

Columns are from A to AO
Rows from 1 to 1300

I have tried on another several other machines but the same error occurs.
I
suspect that this is a corrupt spreadsheet as others are ok. If this is
a
corrupt excel spreadsheet why do you think this may have happened and
how to
prevent it from happening again (also could not find anything on Technet
on
this - are there any articles)? If however it can be fixed please please
let
me know.

Thanks in advance for you help \ suggestions

James


--

Dave Peterson