Wow, after spending far too long debugging this issue, I think I finally figured it out. The query that I was using had a GROUP BY in it (to help me get distinct records). Removing that (and leaving the Flex code alone) fixed my filter function.
Bug? Feature? Or just confused developer? Demian --- In [email protected], "Demian" <[EMAIL PROTECTED]> wrote: > > Rob: > > Thanks for the reply, I've tried that. I've even tried waiting to > assign the filter function until you click the button in question. > Therefore ensuring arraycollection is fully populated before you > attempt to filter it. > > Seems like I most be missing something else. > > Demian > > --- In [email protected], Rob Oates <roboates@> wrote: > > > > I have received that error when I "set" the filter function before > the filter field was initialized. You might try changing where (when) > in your program you set the filter. > > > > Rob Oates > > > > > > > > > > > ____________________________________________________________________________________ > > Get easy, one-click access to your favorites. > > Make Yahoo! your homepage. > > http://www.yahoo.com/r/hs > > >
