Novice Translating from Sql

[egreen]

Hello,

 

I am new to FileMaker, and took a class about databases in college.  I know some sql from that course.  Does anyone know of a good resource that explains Relationships in the context of sql (and E-R Diagrams?), or even FileMaker in comparison to a to a basic database? 

[jbante]

http://www.filemaker.com/support/training/fts.html

[Wim Decorte]

SQL is merely a query language to retrieve data and is a distant secondary to architecture.  ERDs are all about architecture and entities.

 

Do go through the FileMaker FTS training book, the concept of filemaker relationships and table occurrences and context is absolutely crucial.

[egreen]

Clarification--I have gone through the FTS, and payed particular attention to the Data Modeling chapter.  However, the way the data needs to represented in tables seems much too flat.  Additionally, the use of relationships seems to be a combination of an E-R diagram and a table schema.   The anchor bouy design complicates the matter even further, because of the use of table occurrences.  I am looking for an explanation of data modeling that uses database concepts as a reference point.  I mentioned sql because perhaps there is a way to explain what a table occurrence is (is it a join?) through the use of those concepts.

[Wim Decorte]

Can you give an example of what makes you think that "the way the data needs to represented in tables seems much too flat"?  That should give us some insight as to where your blocking points are.

 

Don't think of the FileMaker Define Database Graph as an ERD.  That will save you a lot of grief.

 

A/B is just one of serveral graph /TO management approaches.  Check out the "Approaches to Graph Modeling" white paper: http://www.filemaker.com/technet/techbriefs.html

 

A TO establishes context in FileMaker.  You can only create layouts based on TOs, not on base tables.  Any relationship you create between two TOs is a join in the SQL syntax way.  Any and all scripted actions (new records, set data) always happens from the context of a layout (and hence a TO).  The related data that is available to you also depends on your context (what layout are you on?).

 

If these concepts did not come across properly as you went through the FTS book then I would strongly suggest taking a FTS class where you can really get into it and discuss with the teacher. Or pay an established FM developer for a day of tutoring to get you through this glass ceiling.  These concepts are absolutely vital to get you through the learning curve.