Talk:Documentation/How Tos/Calc: FIND function

I added the 'not found' case because I think it is essential to understanding the FIND() && SEARCH() functions. I elaborate further in the forum that caused me to explore the answer for my own purposes: How to avoid #VALUE!

I would like to re-iterate however, that I believe the definition of the function should be redefined. If I were defining the function, my vote would be for it to return 0 and not #VALUE!. I think #VALUE! is misused in this instance. All of the arguments were legal, the substring simply did not exist.

(< Though, I do understand the difficulty of doing so at this point with the potential of 'breaking' existing spreadsheets that use the ISNUMBER() work around... so perhaps in hindsight I should have abdicated the use of ISERROR() even with the reverse logic?... Perhaps we need an ISVALID() function which is defined as NOT ISERROR() >)

If someone knows of the decision process / rationale behind returning #VALUE! for the FIND() && SEARCH() functions, pls feel free to enlighten me with an e-mail.