Anchor / Buoy Outside Of The Relationship

© 2010 Dwayne Wright - dwaynewright.com
From Dwayne Wright PMP - Certified FileMaker 10, 9 & 8 Developer
EMAIL: info@dwaynewright.com     TWITTER: dwaynewright

As you know, I'm a big fan of the Anchor / Buoy relationship graph technique. When I first discovered it, the only thing missing was a bold ray of light from the sky surrounding my cubicle and a chorus of angels singing "Aaaaahhhhhh".

One day I realized that I have been extending much of the Anchor / Buoy organization strategy beyond relationships and into scripts and layouts. I tend to name my tables with one word and in upper case. This helps with the naming convention I use for the relationships, such as clients_SESSIONS, where the base table is clients and the child table is sessions.

Layout Folder Names - Almost every table that I have has an associated layout folder. That folder is also in upper case and contains a developer layout, form view, list view and often a print layout. They are named with the type in upper case and the detail after.

SESSIONS
    DEV_sessions
    FORM_sessions
    LIST_sessions
    PRINT_sessions
    DIALOG_sessions

Script Folder Names - Almost every table that I have has an associated script folder. That folder is also in upper case and contains scripts organized by their inclusion in a button dock, related record action (GTRR or creation thereof), script trigger actions or any other centralized scripted actions you may have within the solution.

SOME THINGS I AVOID
I have seen developers that use abbreviations throughout their schema names. Usually they have some legend of their abbreviations found in a comments area. I have never embraced this method but I have worked on solutions in which the previous developer used them extensively. I tend to side more towards basic english naming convention.