You don't think they know already? If more than a tiny fraction of their
customer base used VBA and Solver, I doubt they would have released
Office08.
Frankly, among *my* clients who use Solver, most would be better off not
doing so. The average corporate model I audit has so many logic and
numeric errors that Solver simply gives them a false sense of
accomplishment. Sadly, many of them are adaptations of B-school models
that were probably flawed to begin with.
That doesn't mean that SOME Solver apps aren't extraordinarily valuable,
and even flawed apps are sometimes better than nothing.
Hmm... do you know any other company that advertises the shortcomings of
its products (except pharmaceuticals)?
Especially when 90+% of their customers don't even know what Solver *is*.
Don't know that anyone has suggested that AppleScript would be able to
replace Solver. Application-specific solutions are certainly possible,
but I can't imagine a general tool implemented in AS.
And yes, I suspect it *is* that hard to do. Given the enormous amount of
testing that has to be done for even trivial changes, months is hardly
an excessive amount of time, if, in fact, MacBU will be able to come up
with a replacement.
Mr. McGimpsey,
I keep forgetting that one cannot infer my emotions when I write. Lord
knows that I am too old to learn the proper emoticons to use. So, I'll
try to be clearer.
a) When I said that you shouldn't tell Microsoft about many XL users
not using/needing functions, I was 100% sarcastic.
b) When I said that MS should note the absence of Solver in XL08 on
page 1 of their website, I was 50% sarcastic. Maybe not page 1 - but
somewhere! Currently, it is not mentioned at all. When you search the
Mactopia website for "solver", you get many dead ends and finally, a
link to ..... this forum!! When I shop for software, I DO look for
and expect to find things like system compatibility issues. The solver
issue is not (officially) addressed by MS. As I understand it,
disappointed buyers can request a refund, but wouldn't it be better PR
if clarity prevailed?
c) When I said that AppleScript could be used to perform the functions
of solver, I was 75% sarcastic. One of MS's solutions to coping with
the loss of VBA is "create a new macro using AppleScript". Solver uses
AppleScript. Ergo, use AppleScript to make a substitute for Solver.
Okay, I know there's more to Solver than that ... hence, the high
sarcasm index.
Now that I've confessed my sins of omission, I want to comment on how
you've changed the subject from coping with the loss of Solver to:
Solver isn't nearly all it's cracked up to be. Sorry, I don't buy that
at all (0% sarcastic). This falls into the generic GIGO caveat for
computing in general. Bad models and bad data lead to bad results
whether you are taking an average or solving for parameters using
least squares regression. If people are mis-using Solver, either they
were taught incorrectly, forgot what they were taught or weren't
taught at all.
Speaking of GIGO, I'd be interested in learning how MS determined the
degree to which XL users employ Solver. (10% sarcastic).
100% Sincerely,
Jim Dilger