Comments on: Detecting Related Records

By: Gregg O

Gregg O — Tue, 15 Nov 2011 22:31:59 +0000

Be careful when trusting the Get (Last Error) method to check on the validity of your Go to Related Record script step. It is possible to get a 101 error even while the Go to Related Record step has “successfully” completed.

You get a “false” 101 error if all following are true:
1. you select the “Match all records in current found set” option
2. the record on which you happen to be sitting—when the gtrr script step runs—has no related records
3. at least one other originating record has valid related record(s).

In the above case, Filemaker will deliver you to the related found set AND give you a 101 “record is missing” error!

By: William

William — Thu, 29 Sep 2011 13:07:11 +0000

hmm, I use it most of the time. In every table I have a field called One – a number field – which has an auto entered value of 1 – I always assumed this was a safe bet to use. I have never had it fail on it … but these comments are worth considering…

By: Geoff Coffey

Geoff Coffey — Sat, 06 Oct 2007 21:35:40 +0000

@barbara: I’m with you there. I used to use IsValid() for this until I was…ahem…educated on the subject by the FileMaker luminary, Darren Terry several years ago. Luckily, it’s not a hard habit to break. And I agree, I end up using not IsEmpty() most often.

By: Barbara Cooney

Barbara Cooney — Sat, 06 Oct 2007 21:23:59 +0000

I've always used the IsValid() before a GTTR. Hmm. I believe I was taught that it meant "if the relationship is valid..." I'll change to not isempty(), because I typically setup my if elses to be


If positive
 do something
else
 whatever
endif.

Gonna be hard to break the isvalid() habit. Thanks for the tip.