IS functions

D

Dave Unger

Hi Tom,

Ok, this sheds an entirely new light on the subject (for me). I was
under the impression that, whatever qualifier you used (Application,
WorksheetFunction, Application.WorksheetFunction), it was all the same,
the compiler would parse it all down, and generate the same run-time
code. That's why I couldn't understand the different error handling.
But, if it's done by the object, that's a different matter. I don't
think I've come across this in any of my reading, guess I'll have to
delve a little deeper.

Thanks for now,

Dave
 
M

Myrna Larson

never had a problem with Application.Match. These are my own experiences
and Myrna apparently shares those.

Yes. That's been my experience. I've given up on Worksheetfunction.Match. It
isn't worth the hassle.
 
M

Myrna Larson

My experience has also been that WorksheetFunction.Match may cause a run-time
error when in fact there IS a match and I should be getting a numeric result.
In such cases, writing it as Application.Match gives the expected (and
correct) result).
 
B

Bob Phillips

Post XL97?

Bob


Myrna Larson said:
My experience has also been that WorksheetFunction.Match may cause a run-time
error when in fact there IS a match and I should be getting a numeric result.
In such cases, writing it as Application.Match gives the expected (and
correct) result).
 
T

Tom Ogilvy

Since the problem is intermittent, it would be hard to say - added to the
fact that my personal preference is to use Application.Match and iserror -
so not something I have pursued.

--
Regards,
Tom Ogilvy

Bob Phillips said:
Post XL97?

Bob
 
M

Myrna Larson

Hi, Tom:

Are you using On Error Resume Next?

I either do that, or use a Variant variable to receive the result of Match.
The error that I get in the latter situation is something on the order of

Unable to get the Match property of the WorksheetFunction object.

And of course using a variant doesn't help with that. I've never had that
error message with Application.Match.
 
D

Dave Unger

Hello everyone,

Again, I'd like to thank you all for your help, it has been very
educational and is much appreciated.

Dave
 
T

Tom Ogilvy

I've never had that
error message with Application.Match.

I didn't talk about any particular error message. I said I have not pursued
whether it was still a problem in later versions of Excel. So I am not
following your question, but in any event, I am not sure there is any need
to ask one.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top