I suggest doing such filtering on the server side. That way you reduce you transmit less, eliminate the possibility of the full set being intercepted, and remove a layer of complexity from the Flex end. The database is much better suited for this task.
Not trying to dodge your question, so you simply have to refresh your filter.
Hmm, thats for the advice, but i think i would prefer to do it this way, i have it all built out now, and its quite alot of code, its all working, bar this little bit =[
DO yo know how i can resolve it ?
I hope you dont take offence by me not using the method you mentioned.
I'm not seeing where you populate the array. The call to your creationComplete handler seems like overkill though. All you should need to do is fire off a new request to the server. In the result handler, just be sure to apply the filter.
private function qrygetYourJobs(res:ResultEvent):void
YourJobsArr = res.result as ArrayCollection;
I populate the array there, its done on creationComplete.
Im not sure what you meant in your last response, could you explain a bit more please?
Alright, so what happens there is that you create a new ArrayCollection object which (being new) has no filter function set. All that you have to do in the result handler is set the filter funtion and apply the filter with a refresh.
How silly of me