Thanks Andrew, > That's the biggest problem with filter, it's only on one criteria.
That's what I thought too, and I wanted to test it, so I created my filter function with multiple statements ie (psuedocode): if (aRecord.column == passedInVal) or (aRecord.column == 0) return true else return false Which seems to return what I would expect. The list of elements seems to be passed into the filter function fine too... And I assume that as long as the filter function returns true or false everything's sweet. It's only that middle bit - actually checking against the string (the string is really hiding a comma delimited list of values). Of course, I could be competely wrong (in fact, that's likely). > There would be another way that it could be done but I'll have to put my > thinking cap on, am just about to commence a class so I'll try and get > back to this later in the day. Thank you Andrew, I appreciate the help! Sounds like I need one of your classes... you're not planning on a trip to Perth anytime soon? Cheers, Kay, --- You are currently subscribed to fugli as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
