Home |
Search |
Today's Posts |
#10
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
the idea of using a "safe" function is to use the on error method to trap
errors from functions like VLOOKUP and MATCH that raise errors when they fail to find th elookup item and this then means that your usual error handling remains much cleaner...IF you have them :) "Dick Kusleika" wrote in message ... I still get it. I use WorksheetFunction when writing and then delete it. The only thing I don't like is trying to figure out where I want to break long lines. -- Dick Kusleika Excel MVP Daily Dose of Excel www.dicks-blog.com Dave Peterson wrote: One thing that both you and I miss is the intellisense that you get with .worksheetfunction, but I'm willing to live with that loss. Dick Kusleika wrote: Patrick Molloy wrote: Application.Match often used "shortcut" for worksheet functions eg Application.VLookUp instead of Application.WorksheetFunction.VLookUp NOT SAFE. Always use the full syntax. Patrick, Can you elaborate on that. I never use WorksheetFunction so I can trap the errors similar to what Dave did later in this thread. I always thought is was a personal preference, but I'd be interested to know if there's something I'm not considering. -- Dick Kusleika Excel MVP Daily Dose of Excel www.dicks-blog.com |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Type Mismatch | Excel Worksheet Functions | |||
Type Mismatch | Excel Programming | |||
Type mismatch | Excel Programming | |||
Type Mismatch | Excel Programming |