trying to decipher some code

[imoree]

Hey Gang;

just was wondering why would you use the "Evaluate function in this "

 

Case (

Get ( SortState ) = 0

or Get ( SortState ) = 2;

Evaluate ( "Let ( " & ~sortVarIndicator & " = " & Quote ( "" ) & "; False )");

 

~isSameSortField and Get ( SortState );

Evaluate ( "Let ( " & ~sortVarIndicator & " = " & Quote ( ~sortIndicator ) & "; True )");

 

instead of only just using the let ( ) function.

- sometimes i dont know why i should use Evaluate & just Let () .

can someone explain?

-ian

[comment]

why would you use the "Evaluate function in this "

You probably wouldn't. It's hard to say anything more definite without having the context.

[imoree]

Comment; My question was why would you choose to use the Evaluate function vs. just using the Let Funtion.

I know in some cases you want your calcuated field to be a let function sometimes and in a custom function you would use

the evaluate function to encapsulate your calculated field. Or is this all just nonsense or am i just not making sense. I am trying to figure out when to use evaluate in teh proper context..

-i

[comment]

why would you choose to use the Evaluate function vs. just using the Let Funtion.

You would use the Evaluate() function when the formula is not known in advance.

For example, you could give users the choice to select either "+" or "-" in a Operator field, and calculate either the sum or difference of two fields as =

Evaluate ( NumberA & Operator & NumberB )

In practical terms, the need for Evaluate() is rare. The Let() function, BTW, has nothing to do with this.

[Fitch]

Nicely explained.

Just as an example, I've used custom functions constructed with Evaluate and Let when I want to pass name/value pairs as a script parameter, where I want to achieve something like:

Let( *some string of name/value pairs not known in advance* ; result )

Evaluate is AFAIK the only way to do that.

[imoree]

Thank you for the nice explanation Comment..