Calculation sense

[Lee J]

This is more of a generalised question regards the use of Calculation fields.

I have a QuoteItems.fp5 DB which records all the items added to a quote.

It relates to an inventory system and the Actual quote is built up via a portal in the main Quote DB.

The QuoteItems DB is recording alot of information behind the scenes which will be used to produce reports later.

examples are , produce summaries of Group items sold (upto 10), percentage adjustments (discounts)if values get modified in the Quote, showing Group discounts etc

Are there any guidelines you should follow when dealing with multiple calculations so that your system doesn't get bogged down? with performance issues.

cheers in advance

[LiveOak]

Where possible (not used as indices, etc.) don't store the results of calculations, calculate only when needed. Also don't put calc (or summary) fields you don't need on layouts. -bd

[Moon]

May I also suggest that you evaluate all calculations to determine if it could be embedded in a script instead of a calculation field. For instance, if the result of the calculation result is only sometimes required, such as some reports but not others, script it. It can really minimize calculation overhead in complex databases.