Adding watch point "Application.Caller" crashes Edsel 97.

[baobob]

As a Delphi programmer, I'm sincerely trying to adapt to VBA, I really
am.

But, I've got this workbook. I work on it in various versions of
Excel, but right now it's Excel 97 SR2.

First, I set a break point on the first line of code in a function I
wrote. The function is called by referencing it in a cell. E.g., cell
A1 contains "=MyUDF(xxx)".

If I edit cell A1, then exit editing mode, focus jumps to the VBA
environment with execution paused on my break point. Fine. Next I add
a watch point.

If I add, say, watch expression "Application", then, as lovable
Hungarian character actor S. Z. Sakall said in "Christmas in
Connecticut" (1945), "Ev'rysing is hunky-dunky".

But if I so much as add an expression beginning with
"Application.Caller", e.g. "Application.Caller",
"Application.Caller.Address" or something like that, it's Bombs Away
for Excel 1897.

(And if you saw my other recent post, you know I'm having to do my
work amid Excel 97's crashing every time two or more merged cells
happen to show up on row 2841. No joking.)

So, I mean, what's y'all's opinion? Is Excel VBA a stable product, or
is it ... an EDSEL?

Thanks.

***

 

[Charles Williams]

Works fine for me: I can't duplicate the problem.
(I can duplicate your merged cells problem)

Is Excel 97 VBA a stable product?

Well its certainly obsolete ... and all large software products contain bugs
....
but its stable enough for me to still support it (about 100KLOC of VBA
works fine).

regards
Charles
_________________________
FastExcel 2.3
Name Manager 4.0
http://www.DecisionModels.com

 

[Jon Peltier]

While I no longer support Excel 97, I had found it stable enough for the
demands I placed on it. I moved on because 2000 featured an updated VBA
version and other features, and my last Excel 97 client upgraded several
years ago.

I did enjoy the "Edsel" reference, though!

- Jon

 

[baobob]

Charles & Jon:

Thanks very much for your replies.

I'm having continual crashes with Excel SR 2 VBA today again, prompted
by a variety of things.

You're right; I need to upgrade to a more recent Excel. I've got Excel
2002 on my other machine and I don't think it has these problems.

Thanks again.

***