I'm currently having a problem with the speed at which records are listing in one of my layouts. The problem is due to two complex calc fields that take time to recalculate but that have to be shown and that the system forces me to leave unstored. I'm wondering if there's a way I could put something at the end of the calculation so that they set a noncalc field to the value they calculated? That way in the listing I could show the non-calculated fields instead.

It really depends on the situation. If you need something which is altered on the fly, you're stuck with the calculation. If, on the other hand, you've got a calculation which is performed once and then stays at that value (or which is calculated infrequently), you could move the calculation to a script and call the script when you want the standard field altered. This would allow you to index the field and speed up searches, as well as speeding up display of lists.

Your other choice is to run a script every now and then which runs through the whole database and takes your calculated field and puts the result into a standard field. However, you run the risk of using obsolete data that way.

-Stanley

That's what I thought, I was just hoping there was a way to store the last calculation made in a field. It just seems like a lot of excess work for the field to keep recalculating even when the source data that the calculation is dependent on hasn't changed from the last time it made the calculation.