Database Reference
In-Depth Information
FileMaker shows a red icon—it looks surprisingly like a script break-point—by the main
file.
Figure 13-28. The Developer Utilities window (Tools→Developer Utilities) lets you gather the files
you want to change and then tell FileMaker what changes to make. When you're done, click
Create, and FileMaker builds new versions of your files (in a new location) with all the changes in
place.
Renaming Files
Of course, you can always rename a file in Windows Explorer or the Mac's Finder. But doing
this lets you change only the file name. Developer Utilities makes that look like child's play.
When it changes a file name, it also looks inside the file and updates any internal file referen-
ces to match the file's new name. If you've ever tried to open two versions of a multiple file
solution at the same time (to test some scripts that delete data on a copy of the files, say),
then you know FileMaker sometimes gets confused and keeps multiple copies open even
after you try to close one set. You can eliminate the crossover problem by renaming one set
in Developer Utilities. You can test your scripts without a problem, since the scripts in the
copied files automatically inherit the correct new file names.
To rename a file or set of files, add them to the Solution Files list ( Figure 13-28 ). Select a
file; in the “Rename file” box, type the new name and then click Change. FileMaker shows
the new name in the New Name column.
Search WWH ::




Custom Search