The retrieves are based on a single text field, which is not
calculated and which is indexed. Yet the retrieves take 5-10 seconds.
On other DBMSs I am used to an indexed retrieve of a single record
taking maybe 30 milliseconds.

I am after any explanations of why this is happening. Some
possibilities

- The table has 1800 fields, many hundreds of which are calculated.
Yes 1,800.
- The sysadmin does not beleive in unload/reloads or reorgs so it has
not be reorged or unloaded and reloaded for a few years.

Would these factors cause this problem? Any other ideas?

Filemaker server V5.5.

Tim Josling

In article <1180139277.677188.48310 (AT) o11g2000prd (DOT) googlegroups.com>, Tim
Josling <tej (AT) melbpc (DOT) org.au> wrote:

Part of the problem could be that there's a lot of garbage in the file.
Make a backup and then try doing a Save A Copy As (in the File menu)
using the Compressed Copy option. This will keep all the existing
records, structure, etc., but will throw out unneeded rubbish that is
still being kept in the file.

Since you're using a server, you'll need to shut down the server and
perform the save as through a normal copy of FileMaker Pro (do NOT open
the files across the network - copy the files to another computer if
necessary, then open them, Save AS and copy the files back again) and
then restart the server.

If the file is part of a multi-file solution, then you can Save As to a
new filename, quit FileMaker, and then rename the old file to
"XYZ-OLD.fp5" and then rename the new file back to the original
"xyz.fp5" name and the solution will work wiht no problems. You will
probably also need to Save As the other files too.



Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

Tim Josling <tej (AT) melbpc (DOT) org.au> wrote:
I allways create "empty" layouts for all tables, no fields - just the layout.
These layouts are used by scripts accessing the data and save a lot of
processing time. Maybe this will help you to ...

good luck,
Sargasso

In article <465877de$0$97563$dbd49001 (AT) news (DOT) wanadoo.nl>, Sargasso
<no.way (AT) ho (DOT) se> wrote:

Using the Freeze Window command at the start of the script should
achieve almost the same effect - either way FileMaker isn't "slowed
down" by having to update the screen every time you change records (for
example) ... but that isn't going to help a manually performed Find of
course.

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)