Slow calcculations...

[Dan-A]

Hi All,

Any ideas on how to speed up calcs??!!

I added 3 calc to my app and just slowed everything down!!!

They are some time calculations (elapsed time to get duration of events).

I think it's because the "new" calcs use calc fields themselves. Is that possible?

(one set of calcs needs to finish before the other can process)

Also i use some TimeToText function are they known to be slow??

A couple of If statements & Case statements.

Thanks for your thoughts

--Dan

[fishma]

Remove the calculations and set the fields to scripted values residing in numeric fields. Meaning, when the record requires those values to change (be calculated), set the numeric values through a script. When you start reporting, this design feature will pay huge dividends.

[ernst]

Hi Dan,

It makes a huge difference (faster) if the calculation result can be stored. But not all calculations can be stored, for example when a global, or a related field is involved.

Regards,

Ernst

[Dan-A]

Hi Ernst,

I'm not sure if i can store or not??!!

One of the calc fields is the length of the workday.

If i store that calc, what happens if a user changes the start or end time for that day will the length be re-calculated??

When does the calc get "executed" only when the referenced fields have data?

Thanks

-Dan

[ernst]

Hey Dan,

In general stored calculations are calculated at the moment the data changes (thus on entering the data)

Unstored calculations are generated when the calculation result is needed (i.e. for display)

you can easily check if storing is possible by clciking the 'Storage Options...' button in the calculation definition and trying to uncheck the 'Calculate only when needed' option.

Hope this helps,

Ernst.