{"id":1361,"date":"2012-04-14T03:06:02","date_gmt":"2012-04-14T10:06:02","guid":{"rendered":"http:\/\/mclasen.com\/wordpress\/?p=1361"},"modified":"2012-04-14T03:06:02","modified_gmt":"2012-04-14T10:06:02","slug":"filemaker-explore-the-support-group-a-little-bit-of-sql-in-filemaker-12","status":"publish","type":"post","link":"https:\/\/mclasen.com\/wordpress\/2012\/04\/filemaker-explore-the-support-group-a-little-bit-of-sql-in-filemaker-12\/","title":{"rendered":"FileMaker Explore | The Support Group: A little bit of SQL in FileMaker 12"},"content":{"rendered":"
\n
\n
\n

\"read\" –>FileMaker Explore | The Support Group: A little bit of SQL in FileMaker 12<\/a><\/h2>\n
\n

One of my favorite new features of FileMaker Pro 12 is the ExecuteSQL<\/strong> function, which allows you to perform a SELECT SQL query against your FileMaker tables. ExecuteSQL<\/strong> allows you to use SQL to create calculations that otherwise might be very difficult or cumbersome. For example, in the past, if you wanted to get the list of values that had been used anywhere in the field areaCode<\/strong> in your contact<\/strong> table, you had to first create a value list using that field, then create the calculation: ValueListItems ( Get ( FileName ) ; \u201cAreaCodes\u201d )<\/strong>. It worked, but it was a bit of a hack to have to create that extra value list.<\/p>\n

Now, all you need is:<\/p>\n<\/p>\n

\n
\n
\n
ExecuteSQL ( "SELECT DISTINCT areaCode FROM contact" ; "" ; "" ) \/* The last two empty parameters tell FileMaker to use the default comma and carriage return as column and row separators *\/<\/pre>\n<\/div><\/div>\n<\/p><\/div>\n
Okay, so it does require learning a bit of SQL (check out the W3Schools\u2019 SQL Tutorial<\/a>). But many queries are straightforward, and using SQL this way can simplify the relationship graph. <\/p>\n
Say I wanted to get all the area codes used in Massachusetts. Using the old value list method, I would need to create a field somewhere to store the abbreviation \u201cMA\u201d, create a relationship from that field to the contact::state<\/strong> field, and define my value list to use only related values starting from the table with the new field. With ExecuteSQL<\/strong>, all I need is to update the formula to:<\/p>\n
\n
\n
\n
ExecuteSQL ( "SELECT DISTINCT areaCode FROM contact WHERE UPPER(state)=?" ; "" ; "" ; "MA" ) \/* The fourth parameter is used to fill in the ? in the query. It could be a field instead of a text constant *\/<\/pre>\n<\/div><\/div>\n<\/p><\/div>\n
Here\u2019s one of my favorites: often it\u2019s useful to know the name of the base table (the ones define on the Tables tab of the Manage Database dialog) that is the source for a table occurrence (the tables that appear in the graph). You may have lots of table occurrences, named leads<\/strong>, students<\/strong>, personsOfInterest<\/strong>, relatives<\/strong>, and so one, but each is really an instance of the contact<\/strong> table. Outside the Manage Database dialog, any reference to a table is really a reference to a table occurrence (so Get ( LayoutTableName )<\/strong> returns leads<\/strong>, for example, not contact<\/strong>). <\/p>\n
In the past, it would be necessary to name each consistently to include the underlying base table (so contact_leads<\/strong>, contact_students<\/strong>, contact_personsOfInterest<\/strong>, etc.), and then parse the table occurrence name. Be careful changing table names! But with SQL, you can use the following to get the name of the base table of the current layout:<\/p>\n
\n
\n
\n
ExecuteSQL ( "SELECT BaseTableName FROM FileMaker_Tables WHERE TableName=?" ; "" ; "" ; Get ( LayoutTableName ) )<\/pre>\n<\/div><\/div>\n<\/p><\/div>\n
   
 FileMaker_Tables<\/strong> is a special table you can query via SQL to get a list of all table occurrences, and the BaseTableName<\/strong> column tells you the name of the source table.<\/p>\n
You can replace Get ( LayoutTableName )<\/strong> with any table occurrence name to get it\u2019s base table. I like the following calculation field that stores the name of the table as data, which can be extremely useful when exporting and importing data:<\/p>\n
\n
\n
\n
Let ( [ FQFN = GetFieldName ( Self ) ; tableOccurrence = GetValue ( Substitute ( FQFN ; "::" ; \u00b6 ) ; 1 ) ] ; ExecuteSQL ( "SELECT BaseTableName FROM FileMaker_Tables WHERE TableName=?" ; "" ; "" ; tableOccurrence ) )<\/pre>\n<\/div><\/div>\n<\/p><\/div>\n
The two variables in the Let<\/strong> function first get the fully qualified field name (including table occurrence name) of the calculation, an then parses out just the table occurrence name for use in the query. Since the calculation never makes reference to anything but Self, you can copy and paste this calculation field to any table without needing any editing.<\/p>\n
What\u2019s your favorite use of ExecuteSQL<\/strong>? <\/p>\n<\/div><\/div>\n
 <\/p>\n\n\n\n
(Unofficial) Planet FileMaker by Chad Novotny (chad@supportgroup.com<\/a>)<\/span><\/td>\nApril 13, 2012 1:25 PM<\/td>\n<\/tr>\n
<\/td>\n<\/tr>\n<\/table><\/div>\n
\n
Sent from my iPad<\/div>\n
  Posted via email<\/a>   from mclasen’s posterous<\/a>  <\/p>\n<\/p><\/div>\n
<\/p>","protected":false},"excerpt":{"rendered":"
 –>FileMaker Explore | The Support Group: A little bit of SQL in FileMaker 12 One of my favorite new features of FileMaker Pro 12 is the ExecuteSQL function, which allows you to perform a SELECT SQL query against your FileMaker tables. ExecuteSQL allows you to use SQL to create calculations that otherwise might be very […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[3],"tags":[],"class_list":["post-1361","post","type-post","status-publish","format-standard","hentry","category-maccconsulting"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p834Wu-lX","jetpack-related-posts":[],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/posts\/1361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/comments?post=1361"}],"version-history":[{"count":1,"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/posts\/1361\/revisions"}],"predecessor-version":[{"id":1362,"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/posts\/1361\/revisions\/1362"}],"wp:attachment":[{"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/media?parent=1361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/categories?post=1361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mclasen.com\/wordpress\/wp-json\/wp\/v2\/tags?post=1361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}