![]() ![]() It will not work properly in a file that has table occurrence names that are not SQL friendly - for example, having a period in the TO name.Īlso, the script is based on the existence of tables on the relationship graph. There are a couple of things to watch out for when using this script. These table names and fields are available in the three metadata tables: Table Names & Fields Available in the Three Metadata Tables The script now concludes with a dialog indicating that the export is done and where the files can be found. Two additional text files are now saved to the export folder containing a full list of base tables and base fields for the file. We’ve made a couple of additional changes to make the Modular Export script more bulletproof and more useful: The new BaseTableFields table allows us to do the SQL query for the fields in a table with a bit more efficiency than before. This is a single script that can be copied into any FileMaker file to perform a full CSV export of the data in all tables in the file. We’ve taken that update as an opportunity to again improve our modular export script. ![]() ![]() Rather than containing one record for each field in each table occurrence, the new table contains just one field for each base table that exists on the relationship graph. ![]() In FileMaker Pro 19.4, Claris introduced the new FileMaker_BaseTableFields table to the metadata tables accessible via the ODBC interface and the Execute SQL function. PLEASE DOWNLOAD THE CURRENT VERSION, MODULAR EXPORT v1.2, AT THE END OF THIS POST ** **IMPROVEMENTS HAVE BEEN MADE TO THE ORIGINAL DEMO FILE. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |