Database Reference
In-Depth Information
bars, the Windows taskbar or Macintosh Dock, and all other screen decorations that
aren't part of your layouts.
▪ Create a
runtime solution
—a special version of your database that anyone can use, even
if he doesn't have FileMaker Pro.
▪ Permanently remove full access to files so you can send your database to people you
don't know, and be sure they can't tamper with your hard work, including your scripts,
table and field definitions, and Relationships graph.
▪ Create an error log to help you troubleshoot problems that happen when FileMaker gen-
erates runtimes.
In fact, you can (and often want to) do several of these things at once. Here's an example:
You build a beautiful interactive product catalog, complete with pictures and an easy-to-use
ordering screen. You then want to set up a kiosk computer at a trade show where attendees
can use the database to see what you have and place their orders. Using the developer utilit-
ies, you could do all this:
▪ Add “Kiosk” to the end of every file name, so you can keep this copy separate from the
one you use in the office.
▪ Make the database run in Kiosk mode so people at the trade show can't exit FileMaker,
switch to other programs, or otherwise cause mischief.
▪ Make the whole thing run by itself so you don't have to bother installing FileMaker on
the computer you're renting just for this job.
▪ Lock out full access so if someone manages to steal a copy of your database while you're
not looking, she can't see how it works or steal your product's beauty shots.
Using the Developer Utilities
The developer utilities' most confusing aspect is that you have to
close
your files before you
work with them. So close the files you want to modify and then choose Tools→Developer
Utilities. You behold the Developer Utilities window (
Figure 13-28
)
.
In the Developer Utilities window, you first choose which files you want to work with. Click
Add to put a file on the list. In the Open File dialog box, you can select several files at once
by using your Shift and Ctrl (
⌘
) keystrokes. Keep on adding until every file you want to
change is in the list. If you accidentally add the wrong file, select it and then click Remove.
You have to pick one file to be your
main
file. This file is the one that opens first if you cre-
ate a runtime solution, for example. To set the main file, in the list, just double-click it.
