Database Reference
In-Depth Information
UP TO SPEED: WHAT A RECURRING IMPORT IS NOT
Now that you know what a recurring import is, be sure you understand what it is
not
:
▪
It's not synchronization
. Once it's in FileMaker, the data loses all association with the
source file. It's strictly one way.
▪
It's not a merge
. When you switch to a recurring import layout, or push its button, the
import script
deletes every record
in the table and imports them all over again. It doesn't
update existing records or merge the current source file with the changes you made. It
just obliterates the data and brings it in again.
▪
It's not your mom
. Every time you trigger a recurring import, FileMaker looks for the
source file in the exact same place with the exact same name. If you rename it, move it,
or even change the name of the folder that it was in, FileMaker won't look all over your
hard drive to find it for you.
▪
It's not a mind reader
. FileMaker expects the same file, with the same columns, in the
same order, every time. If you're presented with a new version of the source file with,
say, a few new and reordered columns, FileMaker doesn't have a way to sense that and
adjust. It merrily imports the records again, without displaying an error, even if phone
numbers are going into the email address field. And those new columns you added?
Ignored. If the structure of the source file changes, scrap your old recurring import and
then set up a new one.
2.
Answer the dialog box's three questions
:
▪ Does the first row of your import file contain field/column names?
If it does, turn on the checkbox, and FileMaker uses the contents of that row to
name the fields. If you leave the box unchecked, FileMaker names the fields of
your new table f1, f2, f3, and so on.
▪ What do you want to name the new layout?
▪ What do you want to name the script?
For simplicity, FileMaker suggests using the same name as the file you selected. You
can name it something different, but there's no compelling reason to.
3.
Click OK
.
Moments later you have it: a new table, a new field for every column in the source
file, a new script to rerun the import, and a set of freshly imported records on a new
layout (
Figure 21-17
).
