Developer’s Guide

Creating a database solution 2-15
4. In Layout mode, choose Layouts menu > Layout Setup, select Fixed
Page Margins, and specify margins for Top, Bottom, Left, and Right.
Using the Status (CurrentPlatform) function
FileMaker Pro includes a status function that lets you determine the
platform on which the database solution is being run. This allows
you to perform different script actions such as changing to a different
layout or performing a platform-specific script step.
The Status (CurrentPlatform) function returns a 1 when run on a
computer using the Mac OS, a -1 on Mac OS X, a 2 when run on a
computer using Windows 95 or Windows 98, and a -2 when run on
Windows NT systems. Use this function with the If script step to
perform different actions depending on the current platform.
If [“Status (CurrentPlatform) = 1]
Perform Script [Sub-scripts, “Print in Mac OS”]
Else
Perform Script [Sub-scripts, “Print in Windows”]
End If
Creating platform-specific scripts
Although most ScriptMaker steps work on both platforms, some
script steps rely upon platform-specific features. The following steps
are platform-specific:
Windows-only script steps
1 DDE Execute
1 Send Message
1 Insert Object
1 Update Link
Mac OS-only script steps
1 Send Apple Event
1 Perform AppleScript
1 Speak
The Windows Print Setup script step is translated to the Mac OS
Page Setup script step, and vice versa. Note that print options depend
on the printer driver, so that options you save with a script on one
machine may not be available on another. The Send Message script
step (Windows) is translated to the Send Apple Event script step
(Mac OS), and vice versa.
Other platform-specific script steps are skipped when run on a
different platform. Also, platform-specific script steps are shown in
italics when viewed on a different platform.
Your responsibilities as a developer
FileMaker, Inc. has a policy of established procedures for decoding
and repairing passwords. If a customer complies with these
procedures, then FileMaker, Inc. may decode passwords, and/or
supply data or a repaired file for the customer.
If you distribute FileMaker Pro runtime files with passwords, or you
have removed master level design access and you do not want
FileMaker, Inc. to decode passwords, repair access privileges, and/
or return data to a customer who requests such services, you must do
the following:
1. Notify your customers in writing and keep a record of such notice
that your database solution contains passwords and/or data that can
only be provided by you.
2. Every file in your runtime database solution must contain an About
layout accessible from any layout in the database.
See “Adding a custom script to an About menu command” on
page 4-11 and “Creating an About layout” on page 2-8.
3. The layout name must begin with the word “About.”
4. The About layout must contain these items: