Avoiding Summary Fields

[McGoo]

I know that this is not helping the original query but it is a related query that I have and I was wondering if anyone can help me.

I am trying to create a field that will calculate the sum of a value in a field for all the records in the file. I know this is available by creating a summary field but there is so many records in my file this slows my database down considerably when opening it.

[Chuck]

First, does the summary field appear on the layout the user is taken to when the file opens? Does it need to be there? If not, taking it off that layout will speed up the open time.

But, if you really need to have it there and you really need to speed up the time it takes to open the solution, if you have total control of the user's navigational experience, then you can create a global field that you edit by either adding or subtracting to whenever the user might have edited data upon which the summary data would be based.

Let's say you have a layout where the user could have edited information that would affect the summary data. If the user wants to leave that layout they have to use your buttons and scripts. When they enter the layout, using your scripts you copy the data to a global field called perhaps gTempNumber. When they exit the layout, using your scripts, you check to see if they edited data that could affect the summary. If they have, you perform the operation manually.

If [ gTempNumber <> NumberField ]

[BobWeaver]

Beware that this will leave the possibility for the total value to get corrupted for any number of reasons. So, if you want to do that, also provide the means (a script) for the system administrator to do an absolute recalculation of the value occasionally.