Re: Splitting a text string into fields

Dave,
I read your answer and re-read it, and again, but my english, while not
so bad, does not makes me sure to understand fully the message you're
carrying.
Simply said : do you agree on my conclusions : in FMP6 performing a task
with a script may run 10 times quicker than with calculations ?
You made a lot of clever in-sights on how and why but I'd prefer a clear
cut statement at least on the result.
If you don't, then it would mean for me that I am responsible of the
poor performances in calculations with a bad design.
Remi-Noel


"42" <nospam@xxxxxxxxxx> a écrit dans le message de news:
MPG.1df4e5d8a1b33cf1989de4@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> In article <438b3c70$0$9162$626a14ce@xxxxxxxxxxxx>, rnmenegaux@xxxxxxx
> says...
>> > I have no problem writing an 'active' script to do the task, but
>> > really
>> > I'd like do the whole job with calculations. Partly it's
>> > aesthetics,
>> > but also because it's faster.
>>
>> I question that. All experience I have (FMP6) tells me that scripting
>> a
>> task runs it about 10 times faster that doing it through
>> calculations.
>> I can even show you an example.
>> Ten times I say ...
>> Remi-Noel
>
> I've found that this is often based on poorly thought out
> calculations.
> Filemaker doesn't, as far as I know, cache expression evaluations.
>
> One of the big advantages to the Let function is the ability to
> manually
> cache such evaluations. If you've got a complex expression ... e.g.
> involving position, patterncount, substitute, replace, middle words,
> etc
> to build some text, and then within that calculation you need to find
> out its length 4 or 5 times in a case statement, your calc has to
> evaluate that beast 6 or more times.
>
> In a script, you'd just set field a global (or in 8 a variable) of the
> whole mess, and maybe even its length in another, so they only get
> evaluated once. (It makes it easier to read too).
>
> 7/8 provides tools to solve that, (and make calcs easier to read too)
> in
> terms of the let statement, although I find its underused by most
> developers.
>
> On the other hand, poor use of the let statement combined with the
> ability to write recursive custom functions gives those "smart"
> programmers who come up with really neat complex recursive functions
> yet
> who lack any real awareness of complexity theory all the rope they
> need
> to *really* hang themselves.
>
> :D


.

Relevant Pages

  • RE: Unexpected error in Cube Calculations, SSAS 2005
    ... The CALCULATE command controls the aggregation of leaf cells in the cube. ... I click on the Script View and get the error message ... I could then open the script in the "calculations" tab and switch to script ...
    (microsoft.public.sqlserver.olap)
  • Re: Time business inteligence - why it does not work on lowest time level (64bit version)?
    ... I would disagree with you that problem is in script generated by the ... Growth] ... is set to "NA" in calculations. ... Time business inteligence - why it does not work on lowest time ...
    (microsoft.public.sqlserver.olap)
  • Re: window refreshes several times
    ... once I made the script by copying into the script ... the layout did not any longer contain any of the ... calculations are never calculated (as the real calc is made only when needed ... 'Concatenation01', etc. ...
    (comp.databases.filemaker)
  • Re: Splitting a text string into fields
    ... Perhaps you could provide a specific example where your script outperforms ... > performances in calculations with a bad design. ... >> Filemaker doesn't, as far as I know, cache expression evaluations. ... >> out its length 4 or 5 times in a case statement, your calc has to ...
    (comp.databases.filemaker)
  • Re: Unexpected error in Cube Calculations, SSAS 2005
    ... problem in your script fragment is having MEASURES all uppercase. ... cube. ... If the CALCULATE command is deleted or modified, ... I could then open the script in the "calculations" tab and switch ...
    (microsoft.public.sqlserver.olap)