FileMaker Pro 8 Advanced ® Development Guide
© 2005 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries, and ScriptMaker and the file folder logo are trademarks of FileMaker, Inc. All persons and companies listed in the examples are purely fictitious and any resemblance to existing persons and companies is purely coincidental. FileMaker documentation is copyrighted.
Contents Chapter 1 Getting started About FileMaker Pro Advanced Design and develop customized, advanced databases Debug and troubleshoot database solutions Maintain and modify databases New features in FileMaker Pro 8 Advanced Schema sharing features Customizing features Debugging and troubleshooting features Using the FileMaker Pro Advanced documentation Where to find PDF documentation Registration and customer support About the license key Abiding by the license agreement for runtime solutions About the T
FileMaker Pro Advanced Development Guide XML elements and their theme attributes Valid values for theme attributes Specifying default values for themes Using values for patterns and colors Adding comments to theme files Checking theme files for errors Chapter 5 Developing third-party FileMaker plug-ins About external functions About the example plug-in Installing, enabling, and configuring the example plug-in Description of the FMExample plug-in’s external functions Using the example plug-in Customizin
| Chapter 8 Distributing runtime database solutions Organizing solution components Mac OS X runtime application package DLL files for Windows runtime solutions Extensions folder for Windows solutions Choosing a distribution method Reducing solution size Using a custom installation program Using a compression utility program Sharing solutions over a network What your users need Documenting the installation procedures Starting runtime database solutions Recovering damaged files Providing user documentation Cr
FileMaker Pro Advanced Development Guide
Chapter 1 Getting started Welcome to FileMaker® Pro Advanced. This product includes advanced development and customization tools designed especially for database developers. You can use either FileMaker Pro or FileMaker Pro Advanced to create and test your database solutions.
FileMaker Pro Advanced Development Guide New features in FileMaker Pro 8 Advanced FileMaker Pro 8 Advanced includes the following new features and improvements. For a complete listing of new features introduced in FileMaker Pro 8, see the FileMaker Pro User’s Guide or Help. Note If your solution uses third-party plug-ins, contact your plug-in providers to confirm that their plug-ins work with FileMaker 8 products.
Chapter 1 The following manuals are included: 1 FileMaker Pro Advanced Development Guide (this manual): describes how to use the features available in FileMaker Pro Advanced 1 Installation Guide for FileMaker Pro and FileMaker Pro Advanced: contains installation instructions 1 FileMaker Pro User’s Guide: contains key concepts and basic procedures 1 Database Design Report XML Output Grammar manual: describes the FileMaker Pro Advanced Database Design Report (DDR) XML output grammar for users who want t
FileMaker Pro Advanced Development Guide About the license key FileMaker software comes with a unique, 35-character-string license key. Do not lose this license key; it cannot be replaced. We recommend that you keep the license key in a safe place in case the software ever needs to be reinstalled. Important You must enter the license key during installation or the software will not install.
Chapter 2 Customizing database solutions You can use FileMaker Pro Advanced to customize your solutions beyond what is possible with FileMaker Pro. You can: 1 1 1 Add tooltips to provide information about layout objects 1. In Layout mode, select the object to which you want to add a tooltip. Create custom functions for use anywhere within a file 2. Choose Format menu > Set Tooltip.
FileMaker Pro Advanced Development Guide Keep these points in mind: 1 Tooltips display in FileMaker Pro, FileMaker Pro Advanced, runtime database solutions, and databases published to the web with Instant Web Publishing. You must use FileMaker Pro Advanced to add, edit, or delete tooltips.
Chapter 2 | Customizing database solutions 13 1 When you copy or import tables: 1 FileMaker Pro Advanced retains references to tables, fields, and scripts if they are valid when you copy or import. If your tables reference each other through fields, copy or import the tables in one step to retain the references. If you copy or import them one at a time, the references may be lost. Check all references after pasting or importing to ensure they are valid.
FileMaker Pro Advanced Development Guide Importing table schema 1. Open the database file into which you want to import a table. 2. Choose File menu > Define > Database > Tables tab. 3. Click Import. 4. In the Open File dialog box, select the source file. 5. In the Import Tables dialog box, select the tables you want to import from the list and click OK. 6. In the Import Summary dialog box, click Open log file to see a more detailed log of the procedure or click OK to close the dialog box.
Chapter 2 6. Click where you want an item to appear in the formula box. 7. Perform one of the following actions. To add a Do this Reference to a parameter In the parameters list, double-click a parameter name. Mathematical or text operator In the keypad, click an operator. Comparison or logical operator For Operators, choose an operator from the list. Constant value Type the value. Function In the functions list, double-click a function.
FileMaker Pro Advanced Development Guide To change the way functions are sorted in the Define Custom Functions dialog box, choose a category from the View list. Deleting custom functions When you delete a custom function, it is no longer available for use. If you have full access privileges to a database and are editing a calculation that uses a custom function that has been deleted, the name of the function is replaced with the string . To delete a custom function: 1.
Chapter 2 | Customizing database solutions 17 Closing Kiosk solutions To create a Kiosk account: If there is no Quit or Exit button available in your Kiosk solution, users must force-quit the application by pressing Alt+F4 (Windows). Mac OS X version 10.3 (v10.3) users can exit a solution running in Kiosk mode by pressing F9 or F11 to access another open application window. With Mac OS X versions 10.3 and 10.4, users can access other applications by pressing Control-F2.
FileMaker Pro Advanced Development Guide 6. Click Create. If you did not bind the files to a runtime application, the Developer Utilities copy the selected database files to the Project Folder. If you did bind the files to a runtime application, the Developer Utilities copy all of the runtime files to a new folder created inside the Project Folder and named after the runtime solution. The Adjust Window script step may cover up a window that has an Exit Application button.
Chapter 2 | Customizing database solutions 19 To define the dynamic button field: To create the dynamic button script: 1. Choose File menu > Define > Database > Fields tab. 1. Choose Scripts menu > ScriptMaker and click New. 2. Create a field named Icons and make it a Container type. 2. Name the script Toggle Buttons. 3. Click Options > Storage tab. 3. Add a Set Field script step. 4.
FileMaker Pro Advanced Development Guide
Chapter 3 Customizing menus With FileMaker Pro Advanced, you can create custom menus for your database solutions. You can add, edit, duplicate, or delete menus and menu items in many ways, such as: 1 1 Changing a menu item name. Performing a script or script step from a menu item. You can also run scripts from an associated toolbar icon and shortcut menu. 1 1 1 1 Assigning custom keyboard shortcuts and access keys. Specifying a platform for your menus and menu items. Specifying a mode for your menus.
FileMaker Pro Advanced Development Guide How custom menus affect other features Custom menu terminology Custom menus can impact other product features. Keep these points in mind: Before you begin working with custom menus, you should understand the following terms. 1 Term Description Menu bar The area at the top of the screen (Mac OS) or window (Windows) that displays the installed menu set. Menu set The collection of menus that installs on the menu bar. Menu A list of menu items.
Chapter 3 Menu display title Menu bar | Customizing menus 23 Creating and editing custom menus You can create a menu by starting with a blank menu or by editing a copy of a standard FileMaker menu. Menu set (for this file window) Separator Menu You can duplicate a menu so you can make changes without modifying the original or delete menus that your users will not need. To duplicate or delete a menu: 1. Choose File menu > Define > Custom Menus > Custom Menus tab. 2.
FileMaker Pro Advanced Development Guide 2. Do one of the following in the Define Custom Menus dialog box: To Do this Create a menu Click Create. In the Create Custom Menu dialog box, do one of the following, then click OK: 1 1 Click Start with an empty menu Click Start with a standard FileMaker menu, then select a menu from the list. Note You can press Shift and click Create to create an empty menu. Edit an existing menu To Do this Choose a platform for a Select Windows, Macintosh, or both.
Chapter 3 | Customizing menus When you create a menu item that does not have an assigned command, an untitled menu item appears in the Menu Items list of the Edit Custom Menu dialog box. You can then customize the menu item properties. 1. Choose File menu > Define > Custom Menus > Custom Menus tab. 2. In the Define Custom Menus dialog box, select the menu from the list, then click Edit. 3.
FileMaker Pro Advanced Development Guide Keep these points in mind: To Do this Define a shortcut for a menu item Select Shortcut. In the Specify Shortcut dialog box, type the key combination, then click OK. Perform a script or script step when a user selects a menu item Select Action, do one of the following, then click OK. 1 Select Script. In the Specify Script Options dialog box, select a script and enter the optional script parameters as necessary. 1 Select Script Step.
Chapter 3 1 You can modify privilege sets in the Edit Privileges dialog box to control which menu items are enabled. 1 If you set Available menu commands to Editing only or Minimum, menu items based on FileMaker commands are enabled or disabled according to the setting. All other menu items, including items with customized actions, are disabled.
FileMaker Pro Advanced Development Guide To create or edit menu sets: 1. Choose File menu > Define > Custom Menus > Menu Sets tab. Click to remove all menus from the menu set Menu Sets tab in Define Custom Menus dialog box Menus appear in the menu bar in the order shown in this list. Drag an arrow up or down to change the order. Edit Menu Set dialog box 2. Do one of the following in the Define Custom Menus dialog box: To Do this Create a menu set Click Create. 4.
Chapter 3 To Do this Duplicate a menu Select the menu from the list, then click Duplicate. Edit a menu Select the menu, then click Edit. | Customizing menus 29 In the Edit Custom Menu dialog box, edit the menu, then click OK. See “Creating and editing custom menus” on page 23. To duplicate or delete a menu set: 1. Choose File menu > Define > Custom Menus > Menu Sets tab. 2. Do one of the following in the Define Custom Menus dialog box, then click OK.
FileMaker Pro Advanced Development Guide Keep these points in mind: 1 If you choose a menu set other than [File Default], that menu set overrides the selection in the Define Custom Menus dialog box when the layout displays. 1 In Layout mode, select Layouts menu > Set Layout Order to display the Set Layout Order dialog box and review the menu set assigned to each layout. Creating scripts to change menu sets You can create scripts that change menu sets based on conditions that you specify.
Chapter 4 Creating custom layout themes FileMaker Pro and FileMaker Pro Advanced use a variety of layout themes to describe the colors, patterns, fonts, and borders of text, fields, and parts in a new layout. A theme is an Extensible Markup Language (XML) document that can be read and edited in a text editor (such as Notepad for Windows or BBEdit for Mac OS X) or XML editor (such as XML SPY or XMetaL).
FileMaker Pro Advanced Development Guide Important The XML for a layout theme must be well-formed and comply with the required syntax. See “Requirements for theme files” on page 33 and “Checking theme files for errors” on page 41. 4. Change the name of a theme by replacing the value of the THEMENAME element with a new name.
Chapter 4 9. In FileMaker Pro Advanced, choose Layouts menu > New Layout/ Report to use your theme. Follow the instruction in the New Layout/Report assistant. The third panel presents you with a list of themes to select from. | Creating custom layout themes 33 XML resembles HTML in many ways. However, unlike HTML, the XML for layout themes must be well-formed and comply with the required syntax.
FileMaker Pro Advanced Development Guide XML editors expect these characters to be coded as character entities: A single-line element, such as the PEN element, begins with on a single line: Character Coded as ampersand (&) & less than (<) < greater than (>) > apostrophe (‘) ' quote (“) " Using the character instead of the character entity results in an error from the XML editor.
Chapter 4 This multi-lined element is used To describe this layout part Leading grand summary — appears at the beginning of a report and displays a summary field for all the records in a found set. A layout can have only one leading grand summary part.
FileMaker Pro Advanced Development Guide These multi-line elements May contain these elements TITLEHEADERPART FILL HEADERPART FIELD LEADGRANDSUMPART TEXT BODYPART TEXTLABEL TRAILGRANDSUMPART FOOTERPART TITLEFOOTPART LEADSUBSUMPART FILL TRAILSUBSUMPART FIELD BORDER and EFFECT elements share the same pen size. When used together, the pen size value that you set for BORDER will also apply to the EFFECT width.
Chapter 4 These single-line elements Must contain these attributes PEN COLOR PATTERN SIZE Syntax example: SIDES THEMENAME HINT (optional) This attribute COLOR Is used to describe these characteristics And may contain these values RGB color hex values for background fills, text, and borders in layout parts, fields, text blocks, and field labels.
FileMaker Pro Advanced Development Guide This attribute FONT Is used to describe these characteristics And may contain these values The name of the font. More than one font name can be specified, separated by commas. The first font available on a user’s computer will be used in the layout. FONT = “Times New Roman” Note Font values are case sensitive and must be entered in title case with initial capitals.
Chapter 4 This attribute SIZE (for the FONT element) Is used to describe these characteristics And may contain these values This attribute The point size for a font. Any valid point size can be specified. SIZE = “36” STYLE If a font size is unavailable on the computer or for a particular font, FileMaker Pro Advanced will substitute the closest size. SIZE (for the PEN element) Thickness in pixels for the outline of text blocks, field labels, and field borders.
FileMaker Pro Advanced Development Guide Specifying default values for themes 1 2 3 4 5 6 7 8 FileMaker Pro and FileMaker Pro Advanced use default values to replace attributes that are invalid or missing. For each theme listed in a theme file, you can specify whether the default values are determined by the current layout settings, which change when a user changes them, or by standard layout values, which are the same values that FileMaker uses when creating a file for the first time.
Chapter 4 Adding comments to theme files 1 FileMaker Pro and FileMaker Pro Advanced cannot parse an XML theme document that is not well-formed, and they do not validate the XML in your documents. If one required item is missing or wrong, FileMaker Pro Advanced will ignore the entire document. Here is a list of things to check for if your new layout themes don’t appear in the New Layout/Report assistant as expected: 1 1 1 The theme filename has the .fth extension. The theme file is in text format.
FileMaker Pro Advanced Development Guide
Chapter 5 Developing third-party FileMaker plug-ins If you are a C or C++ programmer and familiar with advanced calculations in FileMaker Pro and FileMaker Pro Advanced, you can create external function plug-ins that extend the feature set of the applications. The plug-ins can take advantage of recursion and looping or hook into other programming interfaces.
FileMaker Pro Advanced Development Guide The example plug-in files are located in the English Extras\Examples\FMExample folder on the FileMaker Pro Advanced CD. The plug-in example source code files are located in subfolders in the FMExample plug-in folder. The following tables describe some of the folders and files. Contents of the FMExample folder Folder Description Example folder Contains all of the files that are part of the FMExample.
Chapter 5 | Developing third-party FileMaker plug-ins 45 Installing, enabling, and configuring the example plug-in External function plug-in files must be installed in the appropriate folder and enabled in FileMaker Pro, FileMaker Pro Advanced, FileMaker Server, or FileMaker Server Advanced before they can be used. Some plug-ins must also be configured by the user.
FileMaker Pro Advanced Development Guide Description of the FMExample plug-in’s external functions The FMExample plug-in provided in the Microsoft Visual C++, Apple Xcode, and CodeWarrior example projects adds the following external functions to FileMaker Pro, FileMaker Pro Advanced, FileMaker Server, and FileMaker Server Advanced.
Chapter 5 | Developing third-party FileMaker plug-ins 47 The dialog box that appears when you configure the example plug-in 5. Click OK to use the default format or type a new format. The “#” symbols are replaced by numbers. All other text in the format string is retained as is. 10. Double-click an external function to add it to the formula box. All external function calls require the name of the external function to call and the function’s parameter value, even if the value is null. 6.
FileMaker Pro Advanced Development Guide 12. Continue to build the formula then and click OK when you’re done. 13. Click OK to close the Define Database dialog box. Customizing the plug-in example Customizing FMPluginExample.cpp Make your modifications to the FMPluginExample.cpp in the functions listed in the following table. Function name Customization Do_PluginInit Provide your own unique plug-in ID for “pluginID.” Register each function, providing its name, description, and function to be used.
Chapter 5 | Developing third-party FileMaker plug-ins 49 Requirements for writing external function plug-ins FMExternCallStruct defines the structure of the parameter block. FMExternCallPtr is a pointer to that structure and gFMExternCallPtr is a global variable that should be defined in your code. FileMaker plug-ins are most useful when they contain a single function or a set of functions with similar features.
FileMaker Pro Advanced Development Guide Table of option string characters Characters in the option string Description of characters FileMaker will manage the naming conventions for plug-in name, filename, and function prefix. For this reason, you need to register your plug-in. FileMaker has reserved certain naming conventions for external functions. For more information, see “Registering your plugin” on page 53. 1-4 Characters 1-4 are the plug-in ID.
Chapter 5 There are two possible result values that the plug-in should return in response to the Initialization message: 1 kBadExtnVersion should be returned if the version number passed is less than the value of kMinExtnVersion or greater than the value of kMaxExtnVersion. This prevents the plug-in from running on an API that is incompatible with the API with which it was compiled. 1 kCurrentExtnVersion is the only other result value that should be returned. This causes the plug-in to be enabled.
FileMaker Pro Advanced Development Guide If the idleLevel parameter is not zero, then the routine has been called while the application is running a script or is being controlled by the user. One of the following four messages has been sent: The FMExample plug-in needs to implement a configuration dialog box for the XMpl_UserFormatNumber function, so the flag has been set in the option string (Xmpl1Ynnnnn) and the function Do_PluginPrefs is called when the Preferences message is received.
Chapter 5 | Developing third-party FileMaker plug-ins 53 To avoid potential resource ID conflicts with your plug-in and other applications or plug-ins, follow these guidelines: Registering your plug-in 1 Register your external function plug-in with FileMaker to ensure that it’s unique and not in use by any other plug-in. Registering also allows you to make your plug-in visible to customers searching for a plug-in to suit their needs.
FileMaker Pro Advanced Development Guide
Chapter 6 Debugging, analyzing, and optimizing files The FileMaker Pro Advanced features explained in this chapter are: 1 the Script Debugger for systematic testing and debugging of FileMaker scripts 1 1 1 the Data Viewer for monitoring fields, variables, and calculations the Disable script step feature for testing portions of a script the Database Design Report feature for publishing comprehensive documentation on database schema and options 1 the File Maintenance features for compacting the size of
FileMaker Pro Advanced Development Guide Choose To Choose To Step Execute the script one step at a time. Remove Breakpoints Clear all the breakpoints from the current script. ScriptMaker Halt script execution and open ScriptMaker so you can edit the script. Data Viewer Open (or close) the Data Viewer window so you can monitor specified fields, variables, and calculations.
Chapter 6 Monitoring fields, variables, and calculations You can use the Data Viewer to monitor expressions like field values, local and global variables, and calculations. You can monitor expressions while running scripts or while testing them in the Script Debugger. You can also monitor field values and variables in the database file. | Debugging, analyzing, and optimizing files 57 3.
FileMaker Pro Advanced Development Guide Keep these points in mind: Keep these points in mind: 1 1 1 1 1 1 1 To monitor fields, variables, and calculations of a currently executing script, add them to the Data Viewer list before running the script in the Script Debugger. Expression values in the Data Viewer automatically refresh when using the Script Debugger. Expressions in the Data Viewer window are not removed until you remove them.
Chapter 6 Documenting database schemas Use the Database Design Report (DDR) feature to document the schema of your database and publish it to an HTML or XML file. You can choose which elements and database tables in the database you want to report. The HTML version of the report is hyperlinked and you can view or print it in a Javascript-enabled web browser. With the Database Design Report feature you can: 1 1 1 | Debugging, analyzing, and optimizing files 59 To create a Database Design Report: 1.
FileMaker Pro Advanced Development Guide 5. Clear elements that you want to exclude from the report. By default, all elements in all selected files are reported. Each selected element, if present, will be reported on for each selected file. 6. If you do not want the report to be published in the default HTML format, select XML in the Report Format section. 7. If you do not want the report to automatically open when done, clear the checkbox for this option in the File Handling section.
Chapter 6 The Optimize File option defragments the file to make the physical arrangement of data match the logical arrangement. This feature is especially useful for increasing the speed at which finds and sorts are performed on files with a large number of records. You can use the Optimize File feature at any time, even on databases that will have data added to them. | Debugging, analyzing, and optimizing files 61 1. Open a database file. 2. Choose Tools menu > File Maintenance. 3.
FileMaker Pro Advanced Development Guide
Chapter 7 Using the Developer Utilities FileMaker Pro Advanced provides Developer Utilities that let you: 1 bind your database files into a stand-alone runtime database solution that does not require FileMaker Pro or FileMaker Pro Advanced in order to be used on a computer 1 rename all of your database files and automatically update the internal links to related files and scripts 1 1 display your database files in Kiosk mode remove administrative access from all accounts and prevent users from modify
FileMaker Pro Advanced Development Guide Here are some general considerations for preparing solution files: 1 If desired, create a custom theme for all the layouts in your database solution. See “Creating custom layout themes” on page 31 for information. 1 If you’re creating a solution that will have versions for Windows and Mac OS X, test the different versions of the solution on their respective platforms. For more information, see Help.
Chapter 7 | Using the Developer Utilities 65 6. Under Project Folder, click Specify to choose the location in which the copy of the database solution will be saved. 10. In the Specify Solution Options dialog box, select one or more options. 7. In the Choose a folder for this project’s files dialog box, select or create a folder and click OK (Windows) or Choose (Mac OS X). To Do this Bind databases to runtime applications Choose Create Runtime solution application(s) 8.
FileMaker Pro Advanced Development Guide 12. To be able to quickly repeat the process, click Save Settings, and choose a folder and location for your settings file. See “Saving and reusing Developer Utilities settings” on page 71. 13. Click Create. The Developer Utilities copy all the selected database files, with the modifications made by the Utilities, to the Project Folder.
Chapter 7 1 Will your users be printing reports or other information from your runtime database solution? It’s a good idea to set document margins if your runtime database solution will be printed from a variety of printers. For more information, see Help. 1 Do you want users to be able to perform spell checking on records? You can change the main spelling dictionary language for your database solution by choosing one from the dictionaries supplied with FileMaker Pro Advanced.
FileMaker Pro Advanced Development Guide 4. For File Reference Name, type a name. This is the name that will appear in all lists that display file references. 5. Click OK to save the file reference. Binding files for both platforms If your solution will be used in Windows, bind it using the Developer Utilities for Windows. If your solution will be used on Mac OS X, bind it using the Developer Utilities for Mac OS X.
Chapter 7 To bind database files into a runtime database solution: 1. Follow steps 1 to 9 in “Modifying database solution files” on page 64. 2. In the Specify Solution Options dialog box, select Create Runtime solution application(s). 3. For Runtime Name, type a name for your runtime application. The runtime name is used for the runtime application filename and for the name of the folder that contains the runtime database solution files.
FileMaker Pro Advanced Development Guide The Developer Utilities automatically update all files to use the threecharacter extension that you specify and append the extension to the filenames. Internal file references used in relationships, scripts, and external value lists are updated to interact with the new filenames. Note No matter what the filename extensions are, runtime database files can still be opened in FileMaker Pro and FileMaker Pro Advanced.
Chapter 7 When developing a solution for both platforms, use the same key when you bind the solution in Windows and in the Mac OS X. Also, keep in mind that the binding key is case-sensitive on both Windows and Mac OS X machines. Note Use a binding key you’ll remember and record it in a safe place. (You can do this by saving the Developer Utilities settings file: see “Saving and reusing Developer Utilities settings” on page 71.
FileMaker Pro Advanced Development Guide Converting and upgrading solution files If you have developed a FileMaker Pro runtime database solution using the Solutions Development Kit (SDK) for FileMaker Pro 3.0 or earlier, the Binder utility in the FileMaker Pro 4.0 Developer Edition, or the Developer Tool in FileMaker Developer 5.x and 6.0, you can upgrade your solution and provide your users with the converted files.
Chapter 7 Removing full access privileges from databases FileMaker Pro and FileMaker Pro Advanced use accounts, privilege sets, and extended privileges to protect FileMaker databases. You can use the Developer Utilities to remove all administrative accounts from a file. For more information about accounts and privileges, see Help. Use the Developer Utilities to prevent users from altering the design and structure of your database files and from changing any accounts or privileges that you’ve set up.
FileMaker Pro Advanced Development Guide
Chapter 8 Distributing runtime database solutions The final steps in developing your runtime database solution are to bundle all of the necessary files together, choose how you will distribute your solution—for example, on a CD-ROM or over a network—and provide your users with documentation for installing your solution. In addition, your documentation should include instructions for starting the runtime application and what to do if a file is damaged.
FileMaker Pro Advanced Development Guide DLL files for Windows runtime solutions Extensions folder for Windows solutions The Developer Utilities generate a set of Dynamic Link Libraries (DLLs) during the binding process. These are in the solution folder along with the runtime application and bound database files. They must be delivered as part of the runtime solution. If any of these files are missing or become damaged, they must be replaced.
Chapter 8 | Distributing runtime database solutions 77 3. Open the Dictionaries folder. Using a compression utility program 4. Delete dictionaries for languages not supported by your solution. If your runtime database solution is not complex and you have confidence in the technical experience of your end users, you might consider a compression utility program rather than a custom installation program. To compress files, use a utility such as: Mac OS X 1.
FileMaker Pro Advanced Development Guide Documenting the installation procedures You’ll need to provide instructions to your users on how to install your runtime database solution. Here’s a list of things you should document: 1 Provide written instructions for copying or installing your solution to your users’ hard disks. 1 Include software and instructions specifying how your users can decompress your solution files. 1 Include information about the minimum equipment and software requirements.
Chapter 8 To recover a damaged file: 1 On Windows machines, press Ctrl+Shift while double-clicking the runtime application icon. Hold the keys down until you see the Open Damaged File dialog box. 1 On Mac OS X machines, press Option + 3 while double-clicking the runtime application icon. Hold the keys down until you see the Open Damaged File dialog box.
FileMaker Pro Advanced Development Guide 8. Create a button that lets your users return to the main layout of the primary file. 9. Choose Scripts menu > ScriptMaker and create a script that goes to the About layout. 1 Include the word “About” in the script’s name. 10. Use the Custom Menus feature to create a menu command that displays the About layout. To display the About layout when the runtime application is started: 1. Open the primary file for the database solution. 2.
Chapter 8 | Distributing runtime database solutions 81 Including printed documentation In addition to an online Help system, you should include printed documentation that explains how to install your database solution and briefly how to use it in case users are not able to open your solution files.
FileMaker Pro Advanced Development Guide Your responsibilities as a developer If you distribute database files with passwords or you have removed full access privileges and do not want FileMaker to repair a file for a customer who requests this service, you must: The accounts and privileges protection in a FileMaker file should not be viewed as an absolute barrier that will prevent a customer from accessing files.
Chapter 8 1 Test your runtime database solution with actual data. This is especially important if users are upgrading from earlier versions of the runtime application and need to import data into new solution files. 1 1 Make sure all the auxiliary files and DLLs (Windows) are present. Show your database solution to intended users to uncover any usability issues.
FileMaker Pro Advanced Development Guide
Appendix A Feature comparison of the runtime application with FileMaker Pro When you double-click the FileMaker Pro application icon to start the application, the New Database dialog box opens and you can choose a database file. When you start a FileMaker Pro runtime application, the primary bound database file opens automatically.
FileMaker Pro Advanced Development Guide The Layout tab is changed to the Color tab in the Preferences dialog box for the runtime application. General preferences in a runtime application (Mac OS X) General preferences in a runtime application (Windows) The File Options dialog box does not have the Open/Close and Text tabs in the runtime application, only the Spelling tab—as shown below.
Appendix A | Feature comparison of the runtime application with FileMaker Pro Toolbar comparison Windows The New Database and Open tools in the standard toolbar (in Browse mode, Find mode, and Preview mode) are not available in the runtime application. The Help tool on the standard toolbar in the runtime application is dimmed unless a custom Help script has been specified.
FileMaker Pro Advanced Development Guide Windows Edit Menu command Clear Select All Find/Replace Spelling Object Export Field Contents Sharing Preferences Pro Mac OS X RT 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Browse Mode Find Mode Layout Mode Preview Mode Go to Layout View as Form View as List View as Table Toolbars Status Bar Status Area Text Ruler Pro 1 1 1 1 1 1 1 1 1 1 1 1 RT 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Zoom In Zoom Out Pro Insert Menu command Picture QuickTime Object RT 1 1
Appendix A | Feature comparison of the runtime application with FileMaker Pro Requests Menu command Windows Records Menu command New Record Duplicate Record Delete Record Delete Found Records Go to Record Show All Records Show Omitted Only Omit Record Omit Multiple Modify Last Find Sort Records Unsort Replace Field Contents Relookup Field Contents Revert Record Pro RT 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 (Find mode) Mac OS X 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Pro RT 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
FileMaker Pro Advanced Development Guide Mac OS X (only) Windows Help Menu command Pro FileMaker Pro Help Keyboard Commands FileMaker on the Web Downloads and Updates Register Now About FileMaker Pro About FileMaker Pro Runtime (Displays if no custom About script is specified) About (Displays if custom About script is specified) (Displays if custom Help script is specified) Application Menu command Mac OS X RT 1 1 1 1 1 1 Pro RT 1 1 1 1 1
Appendix A 1 Perform External Script (if the specified file has not been bound to the runtime application) 1 Open File (if the specified file has not been bound to the runtime application) Stored registry settings or preferences Windows registry settings FileMaker Pro stores its registry settings at HKEY_CURRENT_USER\Software\FileMaker\FileMaker Pro\8.0 FileMaker Pro Advanced stores its registry settings at HKEY_CURRENT_USER\Software\FileMaker\FileMaker Pro\8.
FileMaker Pro Advanced Development Guide
Index A About layout 10 creating 80 required contents of 82 access keys, custom menus 22, 25, 26 access privileges 65, 82 accounts and privileges 73, 82 Adjust Window script step 18, 56 administrative accounts removing from a file 73 Allow User Abort script step 56 ampersand (&) character entity 34 apostrophe (’) character entity 34 Apple Computer, Inc.
FileMaker Pro Advanced Development Guide distributing runtime database solutions about 75 distributing updates 83 methods 76 terms and conditions 10 Do_PluginInit function 51 documenting custom menus 22 Database Design Reports 59 database solutions 79, 81 external function plug-ins 53 installation of runtime databases 79 Dynamic Link Libraries (DLLs) 75, 76 E Edit menu commands available in runtime applications 87 electronic documentation 9 elements in layout themes 33 emulating interface elements 18
| importing records 72 See also copying tables 13 Initialization message sent to plug-ins 50 Insert menu commands available in runtime applications 88 install 10 installation code.
FileMaker Pro Advanced Development Guide P package, runtime application (Mac OS X) 75 page margins 67 parts, layout 34 passwords 70, 80 required warning in About layout 82 paths, file 67 pattern palette 40 Pause/Resume Script script step 16 Perform External Script script step 91 performance, improving 60 plug-ins configuring 45, 50, 52 example project 43 function name prefix 50 IDs 49, 50, 53 in runtime applications 85 installing 45 installing web publishing plug-ins 45 preparing 43 registering with Ap
| Scripts menu commands available in runtime applications 89 Scroll Window script step 18 separators, menu item 25 Set Multi-User script step 90 Set Zoom Level script step 18 settings file 71 shortcuts custom menus 26, 27 customizing 26 defined 22 menu item 26 Script Debugger 55 Show Package Contents command (Mac OS X) 75 Show/Hide Status Area script step 18 Shutdown message sent to plug-ins 51 single-line XML elements for layout themes 34 size of database files 60 of solutions 76 Solutions 72 solutions.
FileMaker Pro Advanced Development Guide
