Hi Tom,

See page 53 of "FileMaker Server 12 Custom Web Publishing with XML". As best I can tell Lasso is correctly handing off, and FMS12 is correctly interpreting, the -Operator tags - but I haven't tested them all.

http://www.filemaker.com/support/product/docs/12/fms/fms12_cwp_xml_en.pdf

Keyword FileMaker Pro equivalent operator:

'eq' = '=word'
'cn' = '*word*'
'bw' = 'word*'
'ew' = '*word'
'gt' = '> word'
'gte' = '>= word'
'lt' = '< word'
'lte' = '<= word'
'neq' = omit, 'word'




I'm able to get the range search to work with Lasso 8.6 and FileMaker Server 12, so I'm not sure what the issue might be.

[
local('id_begin'=2000);
local('id_end'=3000);

inline(-Search, -Database='database', -Table='table',-Operator='BW', 'calc_record_id'=#id_begin + '...' + #id_end);
/inline;

]

calc_record_id = Get(RecordID)

This inline tells me my database has 172 records where calc_record_id is between 2000 and 3000. Doing the same search directly in FM confirms this is correct.

One thing I've noticed, at least in the Mac OS, is that typing three dots . . . (minus the spaces) often gets converted to the ellipsis character =85 (not sure what email/Lasso list will do with these). FileMaker should be able to interpret both, but just incase make sure your code editor isn't doing something wonky.

HTH,
Max

____________________________________________
Maxwell Klein Consulting, Inc.
Database Development & Web Integration




On Sep 15, 2013, at 9:21 AM, Tom Langton <tomlangton@verizon.net> wrote:

> Has anyone come up with a definitive list of what passes the default
> "op=bw" filter. Spent a day pulling out remaining hair when trying to move
> a site from FMSA 11 to FMSA 12. The one field that failed with the default
> condition was calculated record ID (a number field, as defined be FM) -
> which was the most used search parameter in the site - folks want to look
> up an item by number very commonly.
>
> At this point I have to go through each action param to see what fails and
> what does not.
>
> Another thing that worked when FMSA 11 is the source, was using the FM
> range option (100=8A120). This does not work with op=eq in Lasso using FMSA
> 12, only finding one record, the first number in the range. That makes
> sense, I guess, but now I have to add another param for the higher number
> and calculate a conditional operator if a range of item numbers is
> requested.
>
> I've not seen documentation to change the default behavior from bw to eq -
> is there a way to do that? I don't think it's a good fix, necessarily,
> just wondering.
>
> Thanks all,
>
> Tom
>
> (Mac OS X.8.6 - LP 8.6.2)
>
> On 8/14/13 2:50 PM, "Maxwell Klein" <lists@maxkdev.com> wrote:
>
>> A couple of things I found with Lasso 8.6 after recently switching from
>> FMS11 to FMS12, which might also apply when using Lasso 8.5=8A.
>>
>> Date searches appear to require the -Operator tag to work at all, and
>> search performance drastically improves when inserting -Operator='EQ' in
>> front of name/value pairs.
>>
>> For example in both cases, this=8A
>>
>> Inline(-Search, -Database='database', -Table='table',
>> 'date_field'=#date_to_find);
>> /Inline;
>>
>> =8Abecomes this=8A
>>
>> Inline(-Search, -Database='database', -Table='table',-Operator='EQ',
>> 'date_field'=#date_local);
>> /Inline;
>>
>> The same inline in FMS11 would work fine, and respond relatively quickly,
>> but in FMS12 -Operator is required for date search and boost performance
>> otherwise. Of course, EQ may not always be the desired action, but in
>> cases where EQ is desired, we're seeing a massive improvement in response
>> times from FMS12 when it's explicitly provided in the inline.
>>
>> I believe the default -Operator action is BW (begins with) when -Operator
>> is not provided, so it appears FMS12 is much faster at EQ (equals)
>> searches.
>>
>> -Max
>>
>>
>>
>>
>> On Aug 12, 2013, at 11:13 PM, Tami Williams <lasso@asktami.com> wrote:
>>
>>> I have FMSA 12 working with Lasso 8.5 and Lasso 9.
>>>
>>> Also - I posted a list of Lasso 9 gotchas that I found when I first
>>> started using it - visible at my twitter feed: @asktami
>>>
>>>
>>>
>>>
>>> On Aug 12, 2013, at 8:24 PM, Brad Lindsay <brad@monkware.com> wrote:
>>>
>>>> Johan,
>>>> Are you saying you have FMSA 12 running with 8.5 or with 8.6 (or both)?
>>>>
>>>> Brad
>>>>
>>>> On 8/12/13, 6:09 PM, Johan Solve wrote:
>>>>> Works fine.
>>>>>
>>>>> But... Two caveats discussed in another thread today:
>>>>>
>>>>> One thing that bit me when migrating from FMS11 to FMS12 is that the
>>>>> date
>>>>> format returned from FM to Lasso has changed into a format that is not
>>>>> directly understood by Lasso. Dates are returned as mm-dd-yyyy from
>>>>> FMS12
>>>>> instead of mm/dd/yyyy previously.
>>>>> This change of behavior might be locale specific as our FM databases
>>>>> have
>>>>> Swedish locale.
>>>>>
>>>>>
>>>>> Another thing I just tracked down is that looping an empty FMS12
>>>>> portal
>>>>> with [portal]...[/portal] container tag seems to crash Lasso. Adding a
>>>>> condition to make sure at least the first related record has a value
>>>>> before
>>>>> looping the portal prevents crashing.
>>>>>
>>>>>
>>>>>
>>>>> 2013/8/12 Ginny White<mvwhite@uoregon.edu>
>>>>>
>>>>>> Hi All -- sorry, probably a question I should know by osmosis from my
>>>>>> years of lurking, but:
>>>>>>
>>>>>> Does Lasso 8.5 work okay with FMSA 12?
>>>>>>
>>>>>> Currently VERY VERY happy with Lasso 8.5 on our Mac OS X 10.6.8
>>>>>> server and
>>>>>> FMSA 11. Whole set up has been very stable for a couple of years,
>>>>>> but we
>>>>>> have to upgrade to FM 12.
>>>>>>
>>>>>> Thanks,
>>>>>> Ginny
>>>>>>
>>>>>> #############################################################
>>>>>>
>>>>>> Attend the Lasso Developer Conference 2013!
>>>>>> Sept 12-14, 2013 in Niagara Falls, Canada
>>>>>> http://www.lassosoft.com/LDC-niagara-falls-2013
>>>>>>
>>>>>> #############################################################
>>>>>> This message is sent to you because you are subscribed to
>>>>>> the mailing list Lasso
>>>>>> Lasso@lists.lassosoft.com
>>>>>> To unsubscribe, E-mail to:<Lasso-unsubscribe@lists.lassosoft.com>
>>>>>> Send administrative queries to<Lasso-request@lists.lassosoft.com>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> #############################################################
>>>>
>>>> Attend the Lasso Developer Conference 2013!
>>>> Sept 12-14, 2013 in Niagara Falls, Canada
>>>> http://www.lassosoft.com/LDC-niagara-falls-2013
>>>>
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso
>>>> Lasso@lists.lassosoft.com
>>>> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
>>>> Send administrative queries to <Lasso-request@lists.lassosoft.com>
>>>
>>>
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> "It's better to burn out than to fade away."
>>>
>>> Tami Williams
>>> Creative Computing
>>> Let us help you make frustrating, costly, and inefficient processes
>>> more efficient, less costly and scalable.
>>> Lasso, MySQL and FileMaker specialists.
>>>
>>> Tel/Fax: 770.457.3221
>>> E-Mail: info@asktami.com
>>> Web: http://www.asktami.com/
>>> LinkedIn: http://www.linkedin.com/in/asktami
>>> Twitter: http://twitter.com/asktami
>>> iChat/AIM/Skype: tamiwilliamsusa
>>>
>>> FileMaker Solutions Alliance Associate | Lasso Professional Alliance
>>> Member | Certified Lasso Developer | FileMaker Certified Developer
>>>
>>> ------
>>>
>>> If you want to receive sporadic email from Creative Computing regarding
>>> news at the company and announcements about upcoming Lasso webinars and
>>> online classes, please opt-in at http://tinyurl.com/yj7eqlg
>>>
>>>
>>> #############################################################
>>>
>>> Attend the Lasso Developer Conference 2013!
>>> Sept 12-14, 2013 in Niagara Falls, Canada
>>> http://www.lassosoft.com/LDC-niagara-falls-2013
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> Lasso@lists.lassosoft.com
>>> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
>>> Send administrative queries to <Lasso-request@lists.lassosoft.com>
>>
>>
>> #############################################################
>>
>> Attend the Lasso Developer Conference 2013!
>> Sept 12-14, 2013 in Niagara Falls, Canada
>> http://www.lassosoft.com/LDC-niagara-falls-2013
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> Lasso@lists.lassosoft.com
>> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
>> Send administrative queries to <Lasso-request@lists.lassosoft.com>
>
>
>
> #############################################################
>
> Attend the Lasso Developer Conference 2013!
> Sept 12-14, 2013 in Niagara Falls, Canada
> http://www.lassosoft.com/LDC-niagara-falls-2013
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> Lasso@lists.lassosoft.com
> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
> Send administrative queries to <Lasso-request@lists.lassosoft.com>


#############################################################

Attend the Lasso Developer Conference 2013!
Sept 12-14, 2013 in Niagara Falls, Canada
http://www.lassosoft.com/LDC-niagara-falls-2013

#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>