OK, so what you're saying is that item.Date_Collected is a string (2008-10-01) and not a date. This goes back to the original suggestion, use a Date() type for that variable in the VO. If you do, then the last sample should work; using selectedDate.
-TH --- In [email protected], Blair Cox <[EMAIL PROTECTED]> wrote: > > Woops, that¹s unpleasant looking. Anyone care to share the proper method of > submitting code? > > -- > Blair > > > > > > From: Blair Cox [EMAIL PROTECTED] > Reply-To: [email protected] > Date: Thu, 23 Oct 2008 16:19:58 -0300 > To: [email protected] > Conversation: [flexcoders] Re: Help: filterFunction and Dates > Subject: Re: [flexcoders] Re: Help: filterFunction and Dates > > > > > Hmm, it doesn¹t actually work. Though I need to try Cato¹s example. See I > discovered this earlier this morning, the .selectedDate actually outputs - > Wed Oct 1 00:00:00 GMT-0300 2008, while I would require 2008-10-01. As I > mentioned, I had it down to 2008-10-1, but choose to manually enter the > variable until I had one part functioning and would come back to the > datefield selection. > > Below is my very hacked sample code I¹m testing with. Please excuse the > mess, but I figured I would provide what I was working with in case I¹ve > missed something. Thanks. > > > <?xml version="1.0" encoding="utf-8"?> <mx:Application > xmlns:mx="http://www.adobe.com/2006/mxml"; layout="vertical"> > <mx:DateFormatter id="dfconv" formatString="YYYY-MM-DD"/> <mx:RemoteObject > id="myservice" source="WorkingDemo"destination="amfphp" > fault="faultHandler(event)" showBusyCursor="true"> <mx:method > name="getUsers" result="resultHandler(event)" fault="faultHandler(_,___ >
