Finally, I abstract the field and table names so that the query doesn’t break if the names end up changing later. If the query has some moderate degree of complexity, I usually end up having to wrap it in Andries Heylen’s sql.debug custom function at least once along the way to troubleshoot what I did wrong. This process involves opening up the Data Viewer and writing out the query there. It just seems faster that way, especially now that I’ve gotten some SQL experience under my belt. Unfortunately, as I create new queries for current projects, I find myself inclined to type them out manually instead of using a wizard (which is how SQL Explorer works). I like the SeedCode SQL Explorer developed by Jason Young. There are several excellent utilities available for constructing SQL queries for use with FileMaker’s ExecuteSQL function.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |