Hello Nelson

I made a two test databases to see if I could test out your scenario.
I can't see why any sorting should be going on. FileMaker does not
automatically sort results of a go to related record command. Can you
give some more information, this may help narrow down the solution:

1. Have you tried rebuilding the index of the field in file B that
relationship is built upon?
2. Do you have any script triggers set in File B to sort on entry to
layout?
3. Is the sort a dialogue box that pops up notifying you to wait while
FileMaker sorts records?
3. What's the full description of the the go to related record script
step - show all related records/only related to current record?
4. Are results show in related file or in a layout in the current
file?

Regards
Kevin Smith

On 30 Sep, 09:49, Nelson <nel... (AT) nowhere (DOT) com> wrote:

Hi Nelson

Coincidentally my test file B also had abut 2,000 records. Thanks for
your detailed feedback. I think it's the index that's corrupted. Every
time file B opens it gets rebuilt. Indexes are prone to corruption.
Here's what you need to do:

1. Do a search in FileMaker's online help file on : "Defining field
indexing options". This will give you background to following steps.
2. Adjust the index of the field that your relationship is based on in
File B (either it's the key field or "Full Name" field depending on
how you've built your database). Set indexing to "None" and "do not
automatically create index as needed"
3. Next, quit database B (I'm not sure if this is 100% necessary, but
it's what I always do)
4. Reopen Database B. Now that index has been removed, reset the
options for the key field: "Do Create indexes as needed". A new, clean
index will be created. Indexing MUST be enabled.

Please let me know how you get along.

Regards
Kevin Smith