I'm very concerned about how FileMaker 7.0v3 handles a go to related record command when there are no records in the child table which satisfy the conditions of the relation. (This is related to the changes which FileMaker made in how a constrain find works if there are no records found.)

If I do a go to RR in a script, and there ARE records which satisfy the relation, the target layout becomes active, and the found set of related records are shown (I thought this was only supposed to happen with a specific show window command, so color me confused.)

If I do a go to RR in a script, and there ARE NO records which satisfy the relation, NOTHING HAPPENS. Instead of the child database showing no found records, as it would've under FMP 6, it shows the previous found set.

What I don't get is this was supposedly addressed with either the v2 or v3 upgrade. As FM says, this should show a found set of zero records:

http://www.filemaker.com/ti/109143.html

So, why is this not happening?

Did I not read this notice from FileMaker correctly?

Should I have sacrificed a chicken over my laptop when I did the upgrade? (I went from v1 to v3, but according to the upgrade docs this should've been fine.)

Help! I really don't want to have to go back through our mammoth multi-db solution and put tests before every go to RR step!

I've attached a very crude file which illustrates the problem.

GoToRelated_Bug_v2.fp7.zip

I think you read it correctly, as far as my understanding of English goes -| It seems either it was not written quite right, or there was a new decision made. Check out this later TechInfo (about a week later), which contradicts the earlier:

http://www.filemaker.com/ti/109176.html

Leave it to FMI to provide cryptic help files.

>>Help! I really don't want to have to go back through our mammoth multi-db solution and put tests before every go to RR step!

Yes, I think you will need to test before the Go to Related Records step to see if there are no related records, or test right after it to see if there was an error.

Yeah, we're putting in a test after each go to rr. What a pain.

One has to wonder what the Filemaker programmers were thinking at times like this. As suggested in an earlier thread, I've taken to testing beforehand, in the context:

If not IsEmpty (relationship)

GTRR

End If

-Terence

I would agree with Murphy, that you should test before. It's easy to do; I almost always have. But it was not previously wrong to test afterwards for a zero found count (though it is now), so I can understand that it's annoying to have to retrofit.

I like the new version. I find myself often using Go To Related Record on buttons, when I want it to go if there are related records, but do nothing if there isnt. The fact that you can now specify a resulting layout means that it can be done in one step; which means it can be attached directly to a button. I sometimes use this, instead of clogging up the Scripts menu with a lot of otherwise unnecessary navigation scripts. It's a lean, mean (and inexpensive) approach to navigation. Unless they change it again -|

I don't know what was going on with those Tech Infos. They were so close together in time, yet opposite in meaning. Of course neither said what the final result actually was; they just said, "it is fixed." Not very explicit.