Subtitles of the Movie

Now let's take a look at exporting data from FileMaker. When we look at importing you saw that I was able to change the sequence of the target fields, but the sequence of the source fields in the data that I am importing could not be changed. What I am going to do now is to export data and you will see now that I can modify the sequence of the source fields. So let me come down here and export some data using export records from the file menu from a database that has some class information form the school. And I can name the file demo export. 0:00:32.0] And all of these format are supported by FileMaker. The two most simple formats 'tab' and 'coma seperated texts' can be read by spread sheets, common databases many word processors and this is sort AF a least common denominator format for data export . These are most sophisticated they work with spreadsheets and with databases. Down here we come to an HTML table which is in export format you may use frequently. You can export data from a FileMaker database into an HTML table that static data can then pasted into a web page. This is different from instant web publishing. Instant web publishing dynamically takes what ever the current data in the FileMaker database is and displays it on the web. The HTML table is the static data that you export as of a certain time and that static data can then be displayed on the web. Each of these technologies is useful for different circumstances. You could also export using a FileMaker format and you can export with XML. For exporting with FileMaker let me just show you one additional feature that you can use . If you save a copy as you can save a copy of the current file with all of its data or clone which is the entire database structure, its scripts, calculations and so forth but with no data. So this is a related way of exporting data to FileMaker. But let's come back into export data to demo export and I am going to use time seperated text. So I have chosen the name and I come here and I have for all of the tables in the database and the related tables the all of the data here. And I can double click, let me first clear all of the fields that I have exported, I can double click, I can select one and click move, I can select a number of fields, and click move and of course I could have clicked move off. These are the fields that I am exporting. And Now because I m exporting I can change the sequence of the fields as they will be exported. So if you are exporting from FileMaker and importing to FileMaker you have the ability to change the sequence both of the export and import files. If you are only exporting you change the sequence of exports, if you are importing you can change the sequence of importing. If the database table is sorted you can group by any of the sort fields. If you have sub summary fields you can then use this to export sub summary data. You would have the sub summary fields in the export fields and you might have identifying fields. The other important issue that you can apply here is to use the current layout state of formatting to the exported data. So that if you have a number that is formatted with comas and decimal points then you can use that formatting for the data that you export. as I supposed to just the raw data of values. Now beware that certain types of import export procedures are not going to be using formatting. So you have to make certain that what you format does get fully exported and imported into the other data store. For example if you are using comas and periods and perhaps spreadsheets indicate negative numbers. If you are importing that data as text all of that will remain, otherwise it may not depending on the application that you are importing data from based on the data that you are exporting from FileMaker. Its a good adventure if you want to play with importing and exporting to use the export command from FileMaker to export data and then just turn around and re-import it, and see what happens as you move the data back and forth , if you are exporting from FileMaker and importing the FileMaker you should have the same results. The one thing that you might want to do if you perform this experiment is save a copy of your database, clone it with no records and use this as the import database, so that you do not get duplicate copies of the data.