Nesting Arguments in Calculation

[Chuck J]

I'm using FM 6 in Windows.

I have run into another situation I can’t seem to resolve. In the following calculation, I need to add another argument. My customer informs me that the following calculation is including jobs that have been finished. She wants me to fix it so no projects that have been finished appear in the list. Where do I put in this calculation that if “Finished” is valid, no calculation should be made for that record.

The fields "Total Jacket Cost" and "CC Total Jacket Cost" in the calculation are in a related database. “Finished” and “Est. Cost” is in the parent database

Case( IsEmpty(Est. Cost),"" , (Main to Action by Jacket::CC Total Jacket Cost + Main to Action by Jacket::Total Jacket Cost)> (Est. Cost * .85), "Approaching Estimate", "")

[Søren Dyhr]

Filemaker doesn't right out of the box provide you with bleedthru Case( statements, this means that first time a true statement is reached the corresponding value is the result because a function only returns one result.

This means that you arrange the conditions as milestones in the reading direction, so the most crutial statement gets attention first.

Case(

Condition1 ; result1;

Condition2 ; result2;

Condition3 ; result3;

result4)

...is the form it better follow.

Then some nitpicking, you'll eventually regret your naming convention using spaces, which makes your calcfields and scripts tough to read and debug. Further reading on naming could be found here:

http://www.codemastersworkshop.com/Downloads/WhitePaperForFMPNovices.pdf

--sd

[Chuck J]

Thasnks for the tip. The whitepaper is the best FileMaker clarifier I have ever read. It will certainly make my solutions more professional. Sometimes in naming fields I catch my errors after the fact, I used a . in one of my field names, a definatye no no.

Thanks again.