WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
Here is a quick list of some of the benefit for Anchor/Buoy
HELPS DEFINE PROPER DATA MODELING
The aspect that no two base table touch directly can be helpful in understanding how each entity in your business model actually works. When you add a new buoy to an anchor, you are basically agreeing to the fact these two business elements communicate via this method.
LAYOUT CONTEXT IS FILTERED
This was the feature that got me drinking the Anchor/Buoy koolaid. In many places, you only see table occurrences that really do link (from a business perspective) to a default base table.
MAKES GREAT USE OF MULTIPLE PREDICATE RELATIONSHIPS
This is because the multiple predicate relationship can easily be identified in other areas and you don’t pick a multiple predicate relationship to use by mistake. This does require that you use the recommended naming convention.
NAMING CONVENTION ALSO INDICATES RELATIONSHIPS OTHER THAN EQUAL TO
Yeah, what I said above. One of the biggest hurdles in advanced FileMaker design is picking the correct table occurrence (and its associated relationship) to use at a given time.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.
© 2008 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.
====================== ADVERTISEMENT ==============================
For more information on the Virtual One On One Training, please visit http://www.dwaynewright.com/training.html===================================================================
Posts
0 comments:
Post a Comment