Rich K. Posted August 18, 2009 Posted August 18, 2009 Hi -- I have been looking at a couple a sample templates and I noticed that they utilize the following technique ... on the Graph they have 2 TO's pointing back to the Inventory Table ... inside the Inventory table they have a a field k_1 ... that is always a "1" and they also have a field called "Catalog_Item" this is set by a user to "1" or "". On the Graph they join (=) between these 2 fields. Which basically narrows the foundset on the Catalog Report. Is this recommended way of narrowing the foundsets? Is there a guide somewhere that shows these best practices? Thanks, Rich K.
bcooney Posted August 18, 2009 Posted August 18, 2009 (edited) Relating a constant 1 to a flag field in a child record doesn't really "narrow the found set." What it does is allow you to go to related records (gtrr) using this relationship, which results in a found set in the child table. But yes, this is a common best practice. In fact, I often suggest, that rather than a checkbox set that contains text values, to use flag fields that equal 1 or 0 or "", so that you can easily gtrr. Edited August 18, 2009 by Guest
Søren Dyhr Posted August 19, 2009 Posted August 19, 2009 (edited) But yes, this is a common best practice. Common practice perhaps, but "best"??? But lets not forget: http://fmhelp.filemaker.com/fmphelp_10/en/html/scripts_ref1.36.74.html --sd Edited August 19, 2009 by Guest
bcooney Posted August 19, 2009 Posted August 19, 2009 Yes, Soren, Constrain found set also works. As usual, it depends on what you are hoping to achieve. Sometimes you need the relationship, sometimes just a quick find would do (with or without a subsequent Constrain).
Recommended Posts
This topic is 5635 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now