| Computers Forum Index » Computer - Databases - Filemaker » Anomalous Re-Sorting Behavior... |
|
Page 1 of 1 |
|
| Author |
Message |
| KevinSmith... |
 Posted: Wed Sep 30, 2009 12:49 pm |
|
|
|
Guest
|
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 (no spam) nowhere.com> wrote:
Quote: Any ideas as to why this might be happening and how to fix it? The
delay while re-sorting is really annoying.
--
Nelson |
|
|
| Back to top |
|
|
|
| Nelson... |
| Posted: Wed Sep 30, 2009 11:04 pm |
|
|
|
Guest
|
On Wed, 30 Sep 2009 08:41:47 -0400, KevinSmith wrote
(in article
<603dd2d8-3cf2-4014-9d6b-0ce8fa13983b at (no spam) y21g2000yqn.googlegroups.com>):
Quote: 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.
Thanks for taking the time. I have about 2100 records in file B. I
suspect with a small enough number of records you wouldn't see the sort
since it would happen so fast.
Quote: 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?
No. The only way I see to do that is through file recovery. Is there
another way?
Quote: 2. Do you have any script triggers set in File B to sort on entry to
layout?
No.
Quote: 3. Is the sort a dialogue box that pops up notifying you to wait while
FileMaker sorts records?
It's not a dialog. Just a progress bar window that says "Sort" and the
number of records left to sort. And in the background you can see the
layout status toolbar clearly saying "sorted" :-)
Quote: 3. What's the full description of the the go to related record script
step - show all related records/only related to current record?
None of the options are checked except "Use Current Layout" in the
external file.
Quote: 4. Are results show in related file or in a layout in the current
file?
As above: shows the record in the current layout in the external file.
A correction to my original post: the sort only seems to happen if
file B is not already open, ie if the GTRR triggers the open. I
suppose I can keep it from happening by leaving the file open but
hidden but I don't understand why I should have to.
Also, if I open file B when file A isn't open, it also doesn't
auto-sort. It only appears to sort if A is already open. And finally,
closing file A and then re-opening it clears the problem... until it
recurs again.
Very strange.
--
Nelson |
|
|
| Back to top |
|
|
|
| KevinSmith... |
| Posted: Thu Oct 01, 2009 10:12 am |
|
|
|
Guest
|
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 |
|
|
| Back to top |
|
|
|
|
