MS Excel Problem

On Fri, 8 Jun 2018 09:38:08 +0100, Chris wrote:

On 07/06/2018 17:11, Ken Blake wrote:
On Wed, 6 Jun 2018 14:43:11 +0100, bobs
wrote:

Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.


Not true. Excel 2016 runs just fine under 64-bit Windows 10 1803 here.

The OP is about Excel 2003.


Maybe. But that's not what the message I replied to says.

Ken Blake wrote:
On Fri, 8 Jun 2018 09:38:08 +0100, Chris wrote:

On 07/06/2018 17:11, Ken Blake wrote:
On Wed, 6 Jun 2018 14:43:11 +0100, bobs
wrote:

Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.


Not true. Excel 2016 runs just fine under 64-bit Windows 10 1803 here.

The OP is about Excel 2003.


Maybe. But that's not what the message I replied to says.


Yes it does. The bits of the message you snipped clearly showed the OP and
the context.

On Fri, 8 Jun 2018 17:24:55 -0000 (UTC), Chris
wrote:

Ken Blake wrote:
On Fri, 8 Jun 2018 09:38:08 +0100, Chris wrote:

On 07/06/2018 17:11, Ken Blake wrote:
On Wed, 6 Jun 2018 14:43:11 +0100, bobs
wrote:

Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.


Not true. Excel 2016 runs just fine under 64-bit Windows 10 1803 here.

The OP is about Excel 2003.


Maybe. But that's not what the message I replied to says.


Yes it does. The bits of the message you snipped clearly showed the OP and
the context.


You are right that SamSpade, in his original message in the thread,
and what bobs quoted, says Excel 2013.

However I replied to what bobs said in the message I replied to.,
quoted in its entirely below:

"Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.
Either revert Windows 10 to an earlier version or wait for MS to
rectify
it (unlikely!!). A work around has been suggested:
1. Select all cells, change justification to something different.
2. Enter you data or whatever.
3. Select all cells, change justification back.
4. Save"

If he meant that "Windows 10 version 1803 (64bit) breaks MS Excel
*2013*," that's what he should have written. He statement as written,
without the "2013," is not correct.

Could I have seen what SamSpade originally said and what bobs quoted?
Yes, of course. But bobs certainly didn't make it easier for me by
saying "MS Excel" if he meant "MS Excel 2013."

In article , Ken Blake
wrote:

On Fri, 8 Jun 2018 17:24:55 -0000 (UTC), Chris
wrote:

Ken Blake wrote:
On Fri, 8 Jun 2018 09:38:08 +0100, Chris wrote:

On 07/06/2018 17:11, Ken Blake wrote:
On Wed, 6 Jun 2018 14:43:11 +0100, bobs
wrote:

Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.

Not true. Excel 2016 runs just fine under 64-bit Windows 10 1803 here.

The OP is about Excel 2003.

Maybe. But that's not what the message I replied to says.

Yes it does. The bits of the message you snipped clearly showed the OP and
the context.


You are right that SamSpade, in his original message in the thread,
and what bobs quoted, says Excel 2013.

no it doesn't.

the post clearly says excel 2003.

nowhere does it say excel 2013 anywhere in the post.

However I replied to what bobs said in the message I replied to.,
quoted in its entirely below:

"Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.
Either revert Windows 10 to an earlier version or wait for MS to
rectify
it (unlikely!!). A work around has been suggested:
1. Select all cells, change justification to something different.
2. Enter you data or whatever.
3. Select all cells, change justification back.
4. Save"

nope. that's not its entirety. you're missing a chunk.

If he meant that "Windows 10 version 1803 (64bit) breaks MS Excel
*2013*," that's what he should have written. He statement as written,
without the "2013," is not correct.

Could I have seen what SamSpade originally said and what bobs quoted?
Yes, of course. But bobs certainly didn't make it easier for me by
saying "MS Excel" if he meant "MS Excel 2013."

you could have, as it was clearly in the post to which you replied,
with excel 2003 (not 2013) in the first line.

below is the message in its entirety:

In article , bobs
wrote:

On 06/06/2018 12:07, wrote:
My Excel 2003 (11.5612.5606) seemingly has gone South.
I only use it to track household expenses, but I have enjoyed it.
Now, however, I cannot enter dollar figures in the cells.
Every time I enter a number, and tab to the next cell, it immediately
exits, failing to save anything I entered.

Interestingly, I can execute the same .xls file to Excel on my other
W10 PC, and it works just fine.

I need help. Sorry if OT.
Sam


Widows 10 version 1803 (64bit) breaks MS Excel but the 32bit is OK.
Either revert Windows 10 to an earlier version or wait for MS to rectify
it (unlikely!!). A work around has been suggested:
1. Select all cells, change justification to something different.
2. Enter you data or whatever.
3. Select all cells, change justification back.
4. Save

On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.

How?


I thought obvious. Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003. I just have to remember to open LibreOffice, not MS Excel.
Sam.

On 9-Jun-2018 12:10 pm, wrote:
On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.
How?

I thought obvious. Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003. I just have to remember to open LibreOffice, not MS Excel.
Sam.

I've been monitoring this thread with concern.

I'm using Excel 2000 with Windows 10 (currently version 1709) and most
of my requirements involve VBA. Excel 2000 works as well as it did with
all the previous Microsoft OSs except for a few very minor points.

The reason I'm still using Excel 2000 is that it does everything I want
- I can't identify any of the "features" offered by the more recent
versions of Excel that I need or want. In particular I found that the
introduction of that ribbon thing made using Excel much harder and the
interface so much more cluttered. So I want to continue using Excel 2000
or similar. I'm even prepared to pay monthly if necessary. But what I
don't want is to have Microsoft crippling Excel 2000 on a more recent
Windows 10 version and have to be forced to go to a more recent version
of Excel which I consider more user-hostile. Obviously I won't be
upgrading Window 10 until I can be sure Excel 2000 will work with a
newer OS.

And, for me, none of the open source alternatives are acceptable as they
don't support the visual basic.

Should I continue to be concerned, or shall I just be flamed for having
such a reactionary attitude?

malone wrote:
On 9-Jun-2018 12:10 pm, wrote:
On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.
How?

I thought obvious. Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003. I just have to remember to open LibreOffice, not MS Excel.
Sam.

I've been monitoring this thread with concern.

I'm using Excel 2000 with Windows 10 (currently version 1709) and most
of my requirements involve VBA. Excel 2000 works as well as it did with
all the previous Microsoft OSs except for a few very minor points.

The reason I'm still using Excel 2000 is that it does everything I want
- I can't identify any of the "features" offered by the more recent
versions of Excel that I need or want. In particular I found that the
introduction of that ribbon thing made using Excel much harder and the
interface so much more cluttered. So I want to continue using Excel 2000
or similar. I'm even prepared to pay monthly if necessary. But what I
don't want is to have Microsoft crippling Excel 2000 on a more recent
Windows 10 version and have to be forced to go to a more recent version
of Excel which I consider more user-hostile. Obviously I won't be
upgrading Window 10 until I can be sure Excel 2000 will work with a
newer OS.

And, for me, none of the open source alternatives are acceptable as they
don't support the visual basic.

Should I continue to be concerned, or shall I just be flamed for having
such a reactionary attitude?


I've got a copy of Office 2000 here.

Why shouldn't I be able to enjoy it ?

It's just software. It doesn't have hardware
drivers or stuff that's easy to break.

Paul

On 9-Jun-2018 2:15 pm, Paul wrote:
malone wrote:
On 9-Jun-2018 12:10 pm, wrote:
On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.
How?

I thought obvious.Â* Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003.Â* I just have to remember to open LibreOffice, not MS Excel.
Sam.

I've been monitoring this thread with concern.

I'm using Excel 2000 with Windows 10 (currently version 1709) and
most of my requirements involve VBA. Excel 2000 works as well as it
did with all the previous Microsoft OSs except for a few very minor
points.

The reason I'm still using Excel 2000 is that it does everything I
want - I can't identify any of the "features" offered by the more
recent versions of Excel that I need or want. In particular I found
that the introduction of that ribbon thing made using Excel much
harder and the interface so much more cluttered. So I want to
continue using Excel 2000 or similar. I'm even prepared to pay
monthly if necessary. But what I don't want is to have Microsoft
crippling Excel 2000 on a more recent Windows 10 version and have to
be forced to go to a more recent version of Excel which I consider
more user-hostile. Obviously I won't be upgrading Window 10 until I
can be sure Excel 2000 will work with a newer OS.

And, for me, none of the open source alternatives are acceptable as
they don't support the visual basic.

Should I continue to be concerned, or shall I just be flamed for
having such a reactionary attitude?


I've got a copy of Office 2000 here.

Why shouldn't I be able to enjoy it ?

It's just software. It doesn't have hardware
drivers or stuff that's easy to break.

Â*Â* Paul

But I'm sure, if they wanted to, Microsoft could incorporate something
in their operating system to prevent it from working properly - as was
suggested earlier in the thread....

"malone" wrote in message
news
On 9-Jun-2018 2:15 pm, Paul wrote:
malone wrote:
On 9-Jun-2018 12:10 pm, wrote:
On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.
How?

I thought obvious. Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003. I just have to remember to open LibreOffice, not MS Excel.
Sam.

I've been monitoring this thread with concern.

I'm using Excel 2000 with Windows 10 (currently version 1709) and most
of my requirements involve VBA. Excel 2000 works as well as it did with
all the previous Microsoft OSs except for a few very minor points.

The reason I'm still using Excel 2000 is that it does everything I
want - I can't identify any of the "features" offered by the more recent
versions of Excel that I need or want. In particular I found that the
introduction of that ribbon thing made using Excel much harder and the
interface so much more cluttered. So I want to continue using Excel 2000
or similar. I'm even prepared to pay monthly if necessary. But what I
don't want is to have Microsoft crippling Excel 2000 on a more recent
Windows 10 version and have to be forced to go to a more recent version
of Excel which I consider more user-hostile. Obviously I won't be
upgrading Window 10 until I can be sure Excel 2000 will work with a
newer OS.

And, for me, none of the open source alternatives are acceptable as they
don't support the visual basic.

Should I continue to be concerned, or shall I just be flamed for having
such a reactionary attitude?


I've got a copy of Office 2000 here.

Why shouldn't I be able to enjoy it ?

It's just software. It doesn't have hardware
drivers or stuff that's easy to break.

Paul

But I'm sure, if they wanted to, Microsoft could incorporate something in
their operating system to prevent it from working properly - as was
suggested earlier in the thread....

As I replied in another thread, I'm still using MS Office 2003 with no
problems. I still use Windows Live Mail 2009 Build 14.0.8117.416, which,
IIRC, wasn't supposed to work any more in Win8.1 or Win10 (don't ask me for
proof of this- it may have been something I read here or in the MS Forums
years ago).

I think if MS really wanted to "break" their older products, they would have
done so years ago. Granted, there are some older programs that won't work
any more in newer versions of Windows, but I would think that's more from OS
code upgrades than from any conscious thought by MS to say, "Hey, let's make
sure Office 97 doesn't work now so people will have to buy our newest
version." Can you imagine how more bloated an OS would be if it had to
support 20-year-old programs? Yikes!!
--

SC Tom

On Fri, 08 Jun 2018 20:10:25 -0400, wrote:

On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.

How?


I thought obvious. Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003. I just have to remember to open LibreOffice, not MS Excel.

I'm glad you took my advice. Seriously though, free software like
LibreOffice will probably be the choice of an increasing amount of
people going forward. I too was burned when Windows 10 suddenly
decided that Corel's software could no longer be installed (without a
work-around) despite being only five years-old and then couldn't
remain stable. My solution was free software and I'll go further in
stating that for every one of my needs in the future, there is a
strong chance that I will only consider open-source options.
Commercial entities have no interest in allowing us to use whatever
software we purchase for any longer than they intend to support it
whereas open-source developers who get absolutely nothing from us
ensure that we always have a tool for whatever job.

On Sat, 9 Jun 2018 13:55:48 +1200, malone
wrote:

On 9-Jun-2018 12:10 pm, wrote:
On Fri, 8 Jun 2018 14:10:38 -0400, "Git" wrote:

On 07/06/2018 00:42, wrote:
My problem is solved, as it usually is.
How?

I thought obvious. Anyway, I can maintain my spreadsheet now, using
LibreOffice, which I could not do suddenly before - using MS Excel
V2003. I just have to remember to open LibreOffice, not MS Excel.
Sam.

I've been monitoring this thread with concern.

I'm using Excel 2000 with Windows 10 (currently version 1709) and most
of my requirements involve VBA. Excel 2000 works as well as it did with
all the previous Microsoft OSs except for a few very minor points.

The reason I'm still using Excel 2000 is that it does everything I want
- I can't identify any of the "features" offered by the more recent
versions of Excel that I need or want. In particular I found that the
introduction of that ribbon thing made using Excel much harder and the
interface so much more cluttered. So I want to continue using Excel 2000
or similar. I'm even prepared to pay monthly if necessary. But what I
don't want is to have Microsoft crippling Excel 2000 on a more recent
Windows 10 version and have to be forced to go to a more recent version
of Excel which I consider more user-hostile. Obviously I won't be
upgrading Window 10 until I can be sure Excel 2000 will work with a
newer OS.

And, for me, none of the open source alternatives are acceptable as they
don't support the visual basic.

Should I continue to be concerned, or shall I just be flamed for having
such a reactionary attitude?

I'm actually glad to hear that such old software still works fine. I'm
hoping that it will continue to do so but I don't trust Microsoft to
allow you to use it for much longer. Their business is software sales
and your decision to use something they deem archaic is a threat to
their bottom line.

On Sat, 09 Jun 2018 09:31:13 -0400, SilverSlimer wrote:


I'm glad you took my advice. Seriously though, free software like
LibreOffice will probably be the choice of an increasing amount of
people going forward. I too was burned when Windows 10 suddenly
decided that Corel's software could no longer be installed (without a
work-around) despite being only five years-old and then couldn't
remain stable.



?? WordPerfect X7 Office runs fine under Windows 10 here.

On Sat, 09 Jun 2018 09:31:13 -0400, SilverSlimer wrote:

I'm glad you took my advice. Seriously though, free software like
LibreOffice will probably be the choice of an increasing amount of
people going forward.

nitpick
People can be counted, so people come in "numbers", not "amounts". :-)

Of course, if you were to put people into an industrial-sized blender,
for example to make the primary ingredient for Soylent Green, once fully
blended they would certainly come in "amounts", as called for by the SG
recipe.

Apologies for the interruption, but that's one of my pet peeves. Please,
carry on.

On Sat, 09 Jun 2018 08:02:15 -0700, Ken Blake
wrote:

On Sat, 09 Jun 2018 09:31:13 -0400, SilverSlimer wrote:


I'm glad you took my advice. Seriously though, free software like
LibreOffice will probably be the choice of an increasing amount of
people going forward. I too was burned when Windows 10 suddenly
decided that Corel's software could no longer be installed (without a
work-around) despite being only five years-old and then couldn't
remain stable.



?? WordPerfect X7 Office runs fine under Windows 10 here.

In this case, it was Corel Video Studio X6.

On Sat, 09 Jun 2018 12:57:41 -0400, SilverSlimer wrote:

On Sat, 09 Jun 2018 08:02:15 -0700, Ken Blake
wrote:

On Sat, 09 Jun 2018 09:31:13 -0400, SilverSlimer wrote:


I'm glad you took my advice. Seriously though, free software like
LibreOffice will probably be the choice of an increasing amount of
people going forward. I too was burned when Windows 10 suddenly
decided that Corel's software could no longer be installed (without a
work-around) despite being only five years-old and then couldn't
remain stable.



?? WordPerfect X7 Office runs fine under Windows 10 here.

In this case, it was Corel Video Studio X6.


OK, thanks for the clarification, but be aware that if you just say
"Corel's software" most people will take that to mean *all* of Corel's
software.