I am writing a calculation intensive relational db. Changing an entry results in a recalculation time of 3-10 seconds depending on machine vintage. Is there a way I can freeze updating of the window while I enter several data points and then recalculate once instead of several times? The data won't/can't be entered in a set order. I might update data fields 1,2 and 5 one time and 2,3, 5 and 8 the next, etc.

The usual answer to this is to make all your fields data fields, and place the formulae into a script (or several scripts) which place calculated results into the relevant fields.

Then you would complete your data entry and click a button labelled 'Calculate' and all the calcs which are dependednt on your data will then be refreshed.

If that doesn't suit, another approach would be to make the calcs unstored (if they aren't already) and then create a separate data entry screen which doesn't have the cals showing (could be the same in all other respects). While you are entering data on the screen without the calcs, they won't calculate, because unstored calcs are only evaluated when they are required for display or other purposes.

The when you finish entering data, you could (again) hit a calculate button which, in this instance, takes you to the layout where the calc results are included -whereupon they will calculate and display.

Thank you Ray. Your first approach just might work. I'll give it a try. The reason the calcs take so long is that it is a pyramid of 3 sets. The first set has about 100 calcs, none of which are or can be stored. The second set depends on the first set and also has about 100 calcs so all of a sudden I am up to 10,000 calcs. For the third set the same thing happens so I am up to a 1,000,000 calcs. If I could force FM to store the intermediate calcs for about 2 seconds I could speed up the process a lot--but I haven't figured out how to do that either.

John