[FX.php List] Solved? Anyone got a sober solution to a date range search?

[Kevin Futter]

On 12/08/08 9:14 AM, "Tim 'Webko' Booth" <tim at nicheit.com.au> wrote:

> 
> On 11/08/2008, at 8:49 PM, Gjermund Gusland Thorsen wrote:
> 
>> I know this worked with Filemaker 5/6
>> ---
>> $q = new FX( $serverIP, $webCompanionPort );
>> $q->SetDBData( $database, 'unit', 'all' );
>> $q->AddDBParam( 'datefield', '1/7/2008...31/7/2008' );
>> $r = $q->FMFind();
>> ---
>> 
>> But what is the FileMaker 7/8/9 equivalent on the XML RPC level to
>> FileMaker's: 1.7.2008...31.7.2008 ?
>> 
>> :-) Hmm it looks like this works! :-) I just played around with the
>> characters and numbers.
>> ---
>> $q = new FX( $serverIP, $webCompanionPort );
>> $q->SetDBData( $database, 'unit', 'all' );
>> $q->AddDBParam( 'datefield', '7.1.2008...7.31.2008' );
>> $r = $q->FMFind();
> 
> Underneath it all, no matter what your localisation settings, all
> dates are now stored MM/DD/YYYY and searches need to be adjusted
> accordingly

I'm not sure (or convinced) that they're stored that way Tim, but they are
certainly presented to the XML interface in that format, no matter what...

Being in Australia too, I make great use of a little swapDateFormat function
whenever dates are involved.

(Internal date storage would be in seconds since epoch, no?)

-- 
Kevin Futter
Webmaster, St. Bernard's College
http://www.sbc.melb.catholic.edu.au/


#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared 
by MailMarshal
#####################################################################################

This e-mail and any attachments may be confidential. You must not disclose or use the information in this e-mail if you are not the intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies. The College does not guarantee that this e-mail is virus or error free.  The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. The content and opinions in this e-mail are not necessarily those of the College.