The Optimizing Filemaker subject has several forums and websites.
Thanks David but I see no alternative in any of the above to solve my problem, this is more than just optimizing scripts and hardware considerations. I still can´t believe that a database software sold to produce reports and be shared over the network is not capable of crunching some numbers (622 records in 2 minutes!) efficiently, why would they even create summary fields in the beginning if filemaker itself claims that you should avoid using summary fields when hosting a database over the network....
I really need a workaround for this or many years of work and money spent is going to be worth for nothing, what is the point of creating a client solution if you can not keep a decent track of each client's balances and monthly sales reports over the network...
Thanks again, and hope anybody can help me with this.
We host from FileMaker server over a network from tables that have over a million records successfully. And they have summary fields. But we also take steps to limit our found sets to avoid unacceptable delays on layouts that need a summary field. But we have also made use of a table of summarized values to reduce the number crunching needed to produce the totals. This is not a method that works for all data models but it has enabled us to produce summary reports spanning 5 years of business transactions (with thousands of records generated each day) without significant delays. (But this is also over a LAN so the circumstances are not nearly as severe as for a WAN.)