Wait, I was mistaken. "Empty" does not work. Using a named range called "null" works, of course, though I'm not sure of the implications thereof.
On Thu, Feb 26, 2015 at 3:03 PM, Blake Watson <blake.wat...@pnmac.com> wrote: > I got this error evaluating a cell--which was a big old chained IF that > return "null" at one point and "undefined" at another, and I think I found > two fixes for it: > > I replaced the null with Empty. > I defined a named ranged called "null" and used that in place of the > undefined. > > For experimental purposes only. I'm not sure how I'll ultimately handle > this. > > Just curious if anyone has run into either of these, and how they handled > it. > > -- > > *Blake Watson* > > *PNMAC* > Application Development Manager > 5898 Condor Drive > Moorpark, CA 93021 > (805) 330.4911 x7742 > blake.wat...@pnmac.com <melanie.petros...@pnmac.com> > www.PennyMacUSA.com <http://www.pennymacusa.com/> > -- *Blake Watson* *PNMAC* Application Development Manager 5898 Condor Drive Moorpark, CA 93021 (805) 330.4911 x7742 blake.wat...@pnmac.com <melanie.petros...@pnmac.com> www.PennyMacUSA.com <http://www.pennymacusa.com/>
