Add numbers in one cell

  • Thread starter Thread starter Raven
  • Start date Start date
R

Raven

Hi there,

I'm trying to add two numbers that are in one cell, but
show the solution in another cell. For example, in cell
A1 I have "1+2,' and in cell B1, I need to show the
solution, "3." Can this be done?

Thanks!
 
One way:

Choose Insert/Name/Define. Enter:

Names In Workbook: EVAL
Refers To: =EVALUATE('Sheet1'!$A$1)


In B1 enter

=EVAL

Note that this uses an XL4M macro - copying it and pasting to another
sheet/workbook can crash XL97/98/00/01/v.X/04
 
JE McGimpsey wrote...
...
Note that this uses an XL4M macro - copying it and pasting to
another sheet/workbook can crash XL97/98/00/01/v.X/04
Click to expand...
...

Are v.X and 04 the Mac counterparts to 2002 and 2003, respectively, fo
Windows? If so, that's odd since it's been reported that this bug ha
been eliminated in 2002 and 2003 (I don't have any version newer tha
2000, so I have no first hand knowledge). I'm not challenging you, jus
asking for confirmation
 
hgrove said:
Are v.X and 04 the Mac counterparts to 2002 and 2003, respectively, for
Windows? If so, that's odd since it's been reported that this bug has
been eliminated in 2002 and 2003 (I don't have any version newer than
2000, so I have no first hand knowledge).
Click to expand...

They're rough counterparts (each has a couple of Mac-only features), but
I suspect the reason the bug's still there is that all MacXL versions
still use VBA5, and therefore I'd guess that the internal object model
and the bulk of the legacy garbage has barely been touched.

MacBU is independent of the Win Office divisions, so has relatively free
rein to include WinOffice changes, or develop their own. Of course, that
doesn't include the basic functionality of XL, which hasn't changed
since XL97/98. But it leads to strange differences - e.g., XL04's stats
showed improvement similar to XL03, but without the negative RAND() bug.

I've submitted the XL4M bug before, but there have been higher
priorities, I guess...

The whole automation effort in XL04 was evidently geared toward
extending the object model to Applescript. MacBU did a great job - Excel
is now nearly 100% applescriptable, and can therefore be run from/by any
Mac app, using the same hooks as VBA. But almost nothing else changed (a
couple old bugs fixed, a couple new ones introduced).

I'm continuing to try to use my vast powers of persuasion to convince
MacBU to update VBA (though the differences mean I can make a decent
income developing cross-platform apps), but frankly, I'd give that up in
a heartbeat if it meant that automation in MacOffice 1x will be
compatible with WinOffice 1x's .Net flavor.

I'm not challenging you, just asking for confirmation.
Click to expand...

Wouldn't have assumed anything different, Harlan!
 
Back
Top