I want to turn off the awful copy and paste functionality that removes what
I have copied inside Excel whenever I press a key, or do any non-paste
related activity. Its making life difficult because it keeps assuming ive
finished with blocks I have in memory.

Any ideas? Registry tweaks? Sledgehammer approaches?

I dont use the multiclipboard thing, and maybe I guess I have to?

This can be a real pain if I use cut, and accidentally misclick because then
I have to undo to get my data back.

Amb

Anyone out there?


"amb" <@> wrote in message news:uNEdi9g%(E-Mail Removed)...
>I want to turn off the awful copy and paste functionality that removes
>what I have copied inside Excel whenever I press a key, or do any non-paste
>related activity. Its making life difficult because it keeps assuming ive
>finished with blocks I have in memory.
>
> Any ideas? Registry tweaks? Sledgehammer approaches?
>
> I dont use the multiclipboard thing, and maybe I guess I have to?
>
> This can be a real pain if I use cut, and accidentally misclick because
> then I have to undo to get my data back.
>
> Amb
>

"amb" <@> wrote...
>Anyone out there?
....

Lots of us, but the only fix for this would be making billions of dollars,
buying Microsoft, and then telling the Excel development staff to fix
Excel's Copy & Paste functionality. The practical alternative is getting
used to Excel's nonstandard AND *NONCHANGEABLE* clipboard functionality.
That's it. There are no fixes for how this works in Excel, and since this is
how Excel has worked for two decades, it's unlikely Microsoft senior
management sees this as something that needs to be fixed. You have to take
this as given and learn to live with it.

> since this is how Excel has worked for two decades

Actually its not. I have an old machine with 98 on it, and it doesnt work
like this.

Anyways, being an eternal optimist, Im sure Microsoft can take note of these
things for future versions.


"Harlan Grove" <(E-Mail Removed)> wrote in message
news:OZN13Dr$(E-Mail Removed)...
> "amb" <@> wrote...
>>Anyone out there?
> ...
>
> Lots of us, but the only fix for this would be making billions of dollars,
> buying Microsoft, and then telling the Excel development staff to fix
> Excel's Copy & Paste functionality. The practical alternative is getting
> used to Excel's nonstandard AND *NONCHANGEABLE* clipboard functionality.
> That's it. There are no fixes for how this works in Excel, and since this
> is how Excel has worked for two decades, it's unlikely Microsoft senior
> management sees this as something that needs to be fixed. You have to take
> this as given and learn to live with it.
>

"amb" <@> wrote...
>>since this is how Excel has worked for two decades
>
>Actually its not. I have an old machine with 98 on it, and it doesnt work
>like this.

What version of Excel? It's worked this way for me in Excel 2, 3, 4, 5, 97,
2K and 2002/XP under various versions of Windows.

If you have an older machine with a version of Excel that works the way you
want, why not use it?

>Anyways, being an eternal optimist, Im sure Microsoft can take note of
>these things for future versions.
....

Like I said, it's always worked this way for me, and with the exception of
Excel 95 (7) and Excel 2003 (11), I've used all the Windows versions. As for
being an optimist about Microsoft software, it helps to have patience. Give
'em another 10 years and they may address this. Then again, Excel's object
model's Application class has a CutCopyMode property, but none of the other
Office applications do. Some would consider that an indication that Excel's
unusual clipboard functionality is intentional.

"Harlan Grove" <(E-Mail Removed)> wrote in message
news:O1jopvs$(E-Mail Removed)...
> "amb" <@> wrote...
>>>since this is how Excel has worked for two decades
>>
>>Actually its not. I have an old machine with 98 on it, and it doesnt work
>>like this.
>
> What version of Excel? It's worked this way for me in Excel 2, 3, 4, 5,
> 97, 2K and 2002/XP under various versions of Windows.
>
> If you have an older machine with a version of Excel that works the way
> you want, why not use it?
>
>>Anyways, being an eternal optimist, Im sure Microsoft can take note of
>>these things for future versions.
> ...
>
> Like I said, it's always worked this way for me, and with the exception of
> Excel 95 (7) and Excel 2003 (11), I've used all the Windows versions. As
> for being an optimist about Microsoft software, it helps to have patience.
> Give 'em another 10 years and they may address this. Then again, Excel's
> object model's Application class has a CutCopyMode property, but none of
> the other Office applications do. Some would consider that an indication
> that Excel's unusual clipboard functionality is intentional.

Don't know if the OP meant win 98 or office/excel 98? If the latter then it
is a Mac version
and that could explain it, if not I agree with you that that's the way it
has worked since I can
remember


--
Regards,

Peo Sjoblom

(No private emails please)