Database Reference
In-Depth Information
▪
Privileges
. Just because
you
can see a given layout, doesn't mean others can. If the recip-
ient of your Snapshot Link lacks the database permissions to see the layout or records
specified in the link, FileMaker won't allow it.
External SQL Sources
If you don't know MySQL from MySpace, and have no interest in taking your humble
FileMaker skills to the hard-core level of IT professionals, then feel free to skip right past
this section. But if you have to cross between these worlds or need to bring the power and
capability of industrial-grade database servers into your systems, then FileMaker's
External
SQL Sources
(or ESS) feature will seem like magic.
In a nutshell, you point your FileMaker database in the general direction of an Oracle, Mi-
crosoft SQL Server, or MySQL (pronounced “my sequel”) database (hereafter referred to as
a SQL database). FileMaker then takes in information about that database, learning all it
needs to know to make those normally complicated systems almost as easy to use as
FileMaker. You can create table occurrences in your Relationships graph that are actually ref-
erences to the tables in the SQL database. You can draw relationship lines between SQL
tables, and even between your FileMaker tables and the SQL tables. You can create a layout
based on a SQL table, drop a few fields on the layout and then jump to Find mode, where
FileMaker searches the real honest-to-goodness SQL data and shows you a found set of re-
cords.
With few exceptions, a SQL table works just like any other FileMaker table. But instead of
storing the data on your hard drive, the SQL database stores and manages the data. You don't
need to know a lick of SQL programming to work with it. When you add a record by using
the Records→New Record command, FileMaker sends the right secret code that adds the re-
cord to the SQL database. Just type in a field and then press Enter, and FileMaker updates
the SQL database. It just doesn't get more seamless than this.
Setting Up ODBC
Before you can take advantage of ESS, you need to set up a few things. This business of get-
ting things installed and configured is the hardest part—and it's not FileMaker's fault.
The SQL Database Server
First of all, you need a SQL database. To integrate as seamlessly as it does, FileMaker needs
to know exactly which database you're using:
▪ Microsoft SQL Server 2012
▪ Microsoft SQL Server 2008
