> Actually, TRUE = anything non-zero (& <> VOID since that's also > treated as zero)
Ooh, Buzz, be careful there. I found out the hard way not to treat VOID as 0 or false. It most definitely is not. I reported this about 18 months ago, and it raised quite a ruckus. It is treated differently on Windows and Mac. I had a 2-day bug in an inherited project on 8.5 that I finally tracked down to this. I forget the exact code, and I can't wade through 4,000 lines of legacy code to track it down at the moment, but it was something like: if NOT (pSomeValue) then or it may have been: if pSomeValue and it evaluated to true on Windows, false on Mac. Whatever the case, if you're going to use a variable in a boolean, and there is any chance at all it could be void, do a check for voidP first. Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
