FOR WINDOWS AND MAC OS DEVELOPER’S GUIDE © 1998 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 http://www.filemaker.com FileMaker and ScriptMaker are trademarks of FileMaker, Inc., registered in the U.S. and other countries. All other trademarks are the property of their respective owners. All persons and companies listed in the examples within are purely fictitious and any resemblance to existing persons or companies is purely coincidental.
iii Contents Chapter 1: Installing FileMaker Pro Developer Edition About this Developer’s Guide Binder application features Remove master access Specify custom menu items Open the runtime application in Kiosk mode New APIs How FileMaker Pro interacts with plug-ins External Function plug-ins Naming and registering your plug-in External function plug-in examples Java class support About Java How the FileMaker Web Companion and Java classes interact About Java classes for FileMaker Pro Java resources on the
iv FileMaker Pro Developer’s Guide Permanently remove access to Define Fields, Define Relationships, ScriptMaker, and Access Privileges Disable runtime solution closing splash screen Use custom “About” script Use custom Help script Rename Script menu Assigning the three-character extension Assigning the extension in Windows Assigning the extension in the Mac OS Changing extensions for cross-platform compatibility Specifying a location for solution files What happens during binding Binding cross-platform so
v Chapter 4: Distributing your bundled solution Organizing your solution files Windows runtime solution files Mac OS runtime solution files Installing items from the Runtime Files folder Contents of the Runtime Files folder Choosing the distribution method Creating a custom installation Compressing your solution Documenting your installation Installing Win32s Creating Win32s diskettes Opening your runtime solution Updating a solution Updating the primary file Adding new or changed auxiliary files Recoveri
Chapter 1: Installing FileMaker Pro Developer Edition Welcome to the FileMaker® Pro 4.0 Developer Edition from FileMaker, Inc. The Developer Edition includes software that’s designed to help you quickly create and deploy standalone FileMaker Pro runtime solutions for your customers. Using the FileMaker Pro Binder software, you create a FileMaker Pro runtime application—a modified version of the FileMaker Pro 4.0 application.
1-2 FileMaker Pro Developer’s Guide About this Developer’s Guide This guide assumes you’re familiar with FileMaker Pro and have created database files. For specific explanations of FileMaker Pro functionality, refer to the FileMaker Pro 4.0 onscreen Help and User’s Guide included with this Developer Edition. Note The Developer’s Guide covers both Microsoft Windows and Mac OS versions of the Developer Edition software. Binder application features This section outlines key features in the FileMaker Pro 4.
Installing FileMaker Pro Developer Edition 1-3 Kiosk mode is ideal for: 1 running your solution files in a retail store, similar to a bookstore directory or gift registry database 1 creating a self-running demonstration or survey 1 disabling access to the operating system while the runtime application is in use See “Run solution in Kiosk mode” on page 2-7 for information and design tips.
1-4 FileMaker Pro Developer’s Guide External Function plug-ins FileMaker Pro 4.0 supports a new API that lets you create External Function plug-ins that add functionality to solutions through the FileMaker Pro calculation engine. For example, you can create plug-ins that: 1 rename, move, or delete files 1 open cash register drawers 1 maintain activity logs You can develop plug-ins for Windows or the Mac OS in C or C++ to process data in FileMaker Pro calculations.
Installing FileMaker Pro Developer Edition 1-5 Preferences dialog box from example plug-in Important FileMaker, Inc. does not provide technical support for third-party plug-ins. Be sure to test your plug-ins carefully. For more information on external function plug-ins, refer to EFP Documentation.pdf: Developer Edition CD\FileMaker Pro APIs\External Function Plug-in\EFP Documentation.pdf.
1-6 FileMaker Pro Developer’s Guide External function plug-in examples There are three sample plug-ins included with the FileMaker Pro Developer Edition: 1 a template example, which is a good starting point for plug-in development 1 a fully functioning plug-in, which has documentation and commented code 1 a folder of external function plug-ins created by third-party developers The template plug-in includes a function that converts characters to their ASCII equivalents (and vice versa).
Installing FileMaker Pro Developer Edition 1-7 Java class support With the new Java API, you can enhance databases you publish on the Web via the FileMaker Web Companion. The Developer Edition also contains information and sample Java applets to help you use the new API. About Java Java is an object-oriented programming language for creating and distributing online applets on the Web. With Java, you can create more sophisticated and useful web sites than you can using HTML alone.
1-8 FileMaker Pro Developer’s Guide How the FileMaker Web Companion and Java classes interact The FileMaker Web Companion can serve information from FileMaker Pro databases to Java applets. Applet programmers take advantage of this by utilizing the Java Class Library in FileMaker Pro 4.0. The library is a set of Java classes FileMaker Pro supports that are compiled with the programmer's Java applet. These classes process FileMaker Web Companion requests, send them to the computer where FileMaker Pro 4.
Installing FileMaker Pro Developer Edition 1-9 1 the names, field types, and value lists (if applicable) for each of the fields on the specified layout, as well as field data 1 record IDs for the returned records This information can be retrieved using the various methods belonging to the response object.
1-10 FileMaker Pro Developer’s Guide To run FileMaker Pro Binder on a Mac OS-compatible computer, you need the following minimum equipment and software: 1 any Macintosh, Power Macintosh, or compatible computer running System 7.1 or later 1 1 1 1 a hard disk 4 MB of RAM (8 MB RAM recommended) a CD-ROM drive solution files developed in FileMaker Pro 4.0 or 3.x Note FileMaker, Inc. recommends using the latest update to the operating system, which is available from Apple Computer, Inc.
Installing FileMaker Pro Developer Edition 1-11 What end users need To run your solution in Windows 3.1, Windows NT, Windows 95, or Windows 98, your end users need the following minimum equipment: 1 an Intel-compatible 486/33 or faster computer with at least 8 MB of RAM 1 a hard disk Note Windows 3.1 requires Win32s 1.30, available in the FileMaker Pro 4.0 folder on the Developer Edition CD-ROM. Additionally, Windows NT 3.51 and Windows 3.
1-12 FileMaker Pro Developer’s Guide Abiding by the license agreement The FileMaker Pro Developer Edition license agreement allows you unlimited, royalty-free distribution of an unlimited number of runtime solutions. However, there are several terms and conditions in the license agreement you must abide by. Among these terms and conditions are the following: 1 You must provide all of the end-user technical support. 1 You must distribute a license agreement with your bundled solution.
Installing FileMaker Pro Developer Edition 1-13 What’s included on the CD-ROMs The FileMaker Pro 4.0 Developer Edition product comes with two CD-ROMs: 1 the Developer Edition CD-ROM 1 the Developer Tools CD-ROM The following table outlines the general contents of the Developer Edition CD-ROM. For more information on the CD contents, see the Developer Edition CD Contents document, located in the Developer Edition CD-ROM.
1-14 FileMaker Pro Developer’s Guide The following table outlines the general contents of the Developer Tools CD-ROM. For more information on the CD contents, see the Developer Tools CD Contents document, located in the Developer Tools CD-ROM. Folder name Description FileMaker Examples and Tools Contains eight folders (below) including sample artwork, database design examples, and general resources FileMaker Examples and Tools\Artwork Sampler Contains over 2,500 pieces of art that can be incorporated
Chapter 2: Binding solution files This chapter describes how to create the bundled solution you’ll distribute to your end users. It assumes you have developed and thoroughly tested the solution files. See chapter 3, “Preparing and managing runtime solutions,” for more information. The binding process—an overview To create a runtime solution using the Binder application, you: 1. Specify the solution’s primary file. 2. Name the runtime application. 3. Assign a binding key. 4.
2-2 FileMaker Pro Developer’s Guide 1 Use a binding key you will remember. If you need to add or update auxiliary files later, rebind the file using the same key. When developing a cross-platform solution, use the same key when you bind the solution in Windows and in the Mac OS. Important For additional considerations before binding, see chapter 3, “Preparing and managing runtime solutions.
Binding solution files 2-3 Specifying the primary file A runtime solution can consist of only one primary file, or a primary file and a set of auxiliary files. The primary file is the database that the runtime application opens first. While it can contain data, the primary file frequently consists of a “Main Menu” layout containing buttons that navigate end users to other database files (auxiliary files). It should also contain an “About” layout and a sample Help script.
2-4 FileMaker Pro Developer’s Guide Naming the runtime solution Specify a name for your runtime solution in the Solution Name text box. The solution filename becomes: 1 the name of the runtime application 1 the name of the solution folder where bound database files are copied To name the runtime solution: 1. In the first panel of the FileMaker Pro Binder application, click in the Solution Name text box. 2. Type a name for your runtime application.
Binding solution files 2-5 To specify the binding key: 1. In the first panel of the FileMaker Pro Binder application, click in the Binding key text box. By default, the binding key is “123456”. 2. Specify the binding key for the runtime application. The binding key must be between 6 and 31 characters and is case-sensitive in the Mac OS. When creating solutions for both the Windows and Mac OS platforms, use the same key for both solutions. 3. Click Next to move to the next Binder panel.
2-6 FileMaker Pro Developer’s Guide To add auxiliary files to the solution: 1. In the second panel of the FileMaker Pro Binder application, click the Add file button. You can specify all the solution files at once by dragging them on top of the FileMaker Binder application. You can also drag auxiliary files directly into the second Binder application panel. 2. Browse through the contents of your hard disk until you locate the files you want to be auxiliary files. 3.
Binding solution files 2-7 Run solution in Kiosk mode Select Run solution in Kiosk mode if you want to provide a special interface for your solution. As in a presentation application or slide show, many of the standard system interface components are removed, such as the menu bar and menu commands, and the screen area around the solution is black.
2-8 FileMaker Pro Developer’s Guide The following table describes how to emulate interface elements that are not shown when you run your solution files in Kiosk mode.
Binding solution files 2-9 Design tips for Kiosk mode Start by planning your database design on paper. Decide what will happen when each button is selected, and give users a way to get back to the beginning from each layout. 1 If your solution will be run with a touch screen, use large buttons and allow space between buttons. 1 Try to limit the number of options available on one screen.
2-10 FileMaker Pro Developer’s Guide This option makes solution files behave as if the Access the entire file and Edit scripts checkboxes in the FileMaker Pro 4.0 Define Passwords dialog box were de-selected. The Access the entire file option restricts access to Define Fields, Define Relationships, and changing Access Privileges passwords and groups. Additionally, the textual version of any calculations you’ve defined (for example, calculation field formulas) is also removed.
Binding solution files 2-11 This replaces the “About FileMaker Pro runtime” menu item in the Help menu (Windows) or in the Apple menu (Mac OS) with the name of the script you specified in the primary solution file. You can also display the “About” layout by: 1 Writing a script that displays the layout each time the end user starts the bundled solution. 1 Displaying the “About” layout when the runtime solution is opened. To do this, in the FileMaker Pro 4.
2-12 FileMaker Pro Developer’s Guide 3. Notify end users if you’ve password protected the solution files or if you’ve selected the Permanently remove access to Define Fields, Define Relationships, ScriptMaker, and Access Privileges binding option. (See “Policy on decoding and repairing passwords” on page 3-6 for the exact legal wording.) 4. Include a button that lets your end users return to the original layout.
Binding solution files 2-13 Selected topic Enter help for the selected topic in this area 2. Edit the layout so that your logo and solution name appear. 3. Select a help topic on the left and then enter the help information on that topic on the right, in the corresponding layout. 4. Make a new layout for each help topic. 5. Modify the Return button script so that it returns end users to your solution. FileMaker, Inc.
2-14 FileMaker Pro Developer’s Guide 2. Type the menu name that replaces the “Script” menu. For example, type “Reports.” The menu name you specify cannot exceed 31 characters. 3. In Windows, specify a keyboard accelerator by typing an ampersand (&) in front of the character you want to become the accelerator key (for example, Address Re&ports will display as Address Reports). Once you’ve specified options on the third panel of the Binder application, click Next.
Binding solution files 2-15 If the three-character extension is not unique, it might cause registry (Windows) or desktop (Mac OS) conflicts. For example, if you use the “.fp3” extension and your end users have FileMaker Pro installed on their hard disks, their FileMaker Pro document icons (and application icon in the Mac OS) will change to the runtime icons. Additionally, FileMaker Pro documents will no longer automatically open the FileMaker Pro application.
2-16 FileMaker Pro Developer’s Guide Assigning the extension in the Mac OS In the Mac OS, the three-character extension becomes the creator code for the runtime application. The creator code must be unique to ensure that the Finder in Mac OS can determine which application created each document. The creator code is stored in both the solution files and the runtime application. Because creator codes are four characters, FileMaker Pro Binder inserts an uppercase F after the first character.
Binding solution files 2-17 Changing extensions for cross-platform compatibility If you’re binding solution files on the Mac OS and creating a solution to run in both Windows and the Mac OS, select the Change filenames for Windows compatibility option in the fourth binding panel. The Binder application automatically updates all filenames to use the three-character extension specified during binding.
2-18 FileMaker Pro Developer’s Guide In the Mac OS, click the folder name to put it in the Select “” button at the bottom of the dialog box. 3. In Windows, double-click the folder name and click OK. In the Mac OS, click the Select “” button. Windows Click to specify the solution folder Mac OS 4. In the fifth panel, click the Finish (Windows) or Bind (Mac OS) button to bind the new runtime application to the solution files. Or, click the Back button to review your binding options.
Binding solution files 2-19 What happens during binding When you click the Finish button (Windows) or the Bind button (Mac OS), FileMaker Pro Binder performs the following activities: 1 saves a copy of the solution files into the folder specified in the Runtime application icon fifth panel 1 updates the solution files with binding options, such as adding three-character extensions or renaming menu items Primary file icon 1 generates a runtime application 1 binds the runtime application with the specif
2-20 FileMaker Pro Developer’s Guide Binding cross-platform solutions If you’re creating a solution to run on both Windows and the Mac OS, bind the solution files twice: first using FileMaker Pro Binder for Windows, and then using FileMaker Pro Binder for the Mac OS. Use the same binding key on both platforms. Remember that binding keys are case-sensitive in the Mac OS.
Chapter 3: Preparing and managing runtime solutions This chapter describes: 1 1 1 1 1 1 preparing your files before binding protecting your files with passwords FileMaker, Inc.
3-2 FileMaker Pro Developer’s Guide 4. Create a Help system that provides usage and navigational tips for your solution. The Help files contained in the FileMaker Pro application cannot be distributed with the FileMaker Pro runtime application. Explore the sample integrated help system: Developer Tools\FileMaker Examples and Tools\Runtime Solution Example. See “Use custom Help script” on page 2-12 for more information. 5. Use the FileMaker Pro Binder application to bind the primary and auxiliary files.
Preparing and managing runtime solutions 3-3 1 Is the runtime application operating in Kiosk mode? If your solution is running in Kiosk mode, the entire interface must be accessible via buttons on the layouts. Include an Exit or Quit button if the file needs to be closed. 1 Does the runtime solution contain auxiliary files? Place a “Main Menu” button or startup script in each auxiliary file that moves end users to the primary file. See “Choosing auxiliary files” on page 2-5 for more information.
3-4 FileMaker Pro Developer’s Guide Documenting your files Although much of your documentation might be in a custom Help file, you should create and distribute printed documentation for your solution to cover items not appropriate or useful in help.
Preparing and managing runtime solutions 3-5 Protecting your solution files To prevent end users from modifying the database structure, you should define passwords in the FileMaker Pro files before binding. Solution files can be opened in FileMaker Pro 4.0; if they don’t have passwords, end users can access and modify scripts, field definitions, access privileges, and layouts.
3-6 FileMaker Pro Developer’s Guide Policy on decoding and repairing passwords FileMaker, Inc. has established procedures, and if a customer complies with these procedures, then FileMaker, Inc. will decode passwords, and/or supply data or a repaired file for such customer. This policy is outlined in the FileMaker, Inc. document entitled “Unlocking Password Protected Files.” This document can be accessed via the support area of our web site: http://www.filemaker.com or through the FileMaker, Inc.
Preparing and managing runtime solutions 3-7 FileMaker, Inc. is unable to, and will not, investigate any requests to verify the truth of statements submitted by the requester beyond what is required by our procedures. This process has been invaluable to numerous customers who have legitimately been unable to access their valuable files. The password protection in a FileMaker file should not be viewed as an absolute barrier which will prevent a customer from accessing files. FileMaker, Inc.
3-8 FileMaker Pro Developer’s Guide 1 Test your solution with actual data. This is especially important if end users are upgrading from earlier versions of the runtime application and need to import data into new solution files. 1 Make sure all the auxiliary files and DLLs (Windows) are present. 1 Show your solution to intended end users to uncover any usability issues.
Preparing and managing runtime solutions 3-9 You can add more fonts to the Registry Editor to include more font substitutions. If there is no match and no substitute is defined, FileMaker Pro changes the font to Arial. In the Mac OS, FileMaker Pro attempts to substitute a similar font.
3-10 FileMaker Pro Developer’s Guide The following are examples of characters that won’t display properly across platforms: Windows-only characters: 1 1/4 symbol 1 1/2 symbol 1 3/4 symbol Mac OS-only characters: 1 1 1 1 ≠ (not equal sign) ≥ (greater than or equal to) ≤ (less than or equal to) √ (square root/check mark) Color palettes When 256 or more colors are available, FileMaker Pro will offer an 88-color palette that is virtually identical across platforms.
Preparing and managing runtime solutions 3-11 Graphics If you’re storing and displaying graphics across platforms, be sure to select the Document Preference for Store compatible graphics before importing the graphic. Then two copies of the graphic image will be stored: the original version (for example, bitmap, metafile, or GIF) as well as a PICT file format.
3-12 FileMaker Pro Developer’s Guide Text bounding box too narrow Make the field deeper to accommodate substituted fonts Text bounding box too shallow Make the text object wide enough to accommodate font substitution Verify alignment of text objects Check the alignment of the field labels and their associated fields—they should both be aligned in the same direction. If you put a left-aligned label over a column of right-aligned numbers, for example, the report might look fine on your computer.
Preparing and managing runtime solutions 3-13 Note If your file exchange utility doesn’t handle long filenames between Windows 95 or Windows NT and the Mac OS, relationships and scripts may fail. Contact your local software dealer for information on software that helps you transfer data across platforms.
3-14 FileMaker Pro Developer’s Guide Printing tips Scripts that include Page Setup/Print Setup and Print are not 100% compatible cross-platform. The print steps in ScriptMaker rely upon the current printer driver in order to determine the paper sizes that are available, page orientation, and so on.
Preparing and managing runtime solutions 3-15 The first time you play a movie from the other platform (that is, a Windows movie in the Mac OS or a Mac OS movie in Windows), FileMaker Pro prompts you for the location of the movie. Keep the files in a common folder and avoid choosing the wrong file—this could lead to unexpected results. Creating cross-platform scripts Though most ScriptMaker steps work cross-platform, some steps rely upon or take advantage of platform-specific features.
3-16 FileMaker Pro Developer’s Guide Converting and upgrading solution files This section assumes you have developed a solution in the FileMaker Pro 3.0 or earlier Solutions Development Kit (SDK) and want to update your end users to FileMaker Pro 4.0 Developer Edition. Here is an overview to updating your solution files: 1. Convert each solution file to FileMaker Pro 4.0. 2. If you want, update your solution files to take advantage of FileMaker Pro 4.
Preparing and managing runtime solutions 3-17 4. Create scripts that import data from the original files into the updated solution files. The original solution files will be converted when end users execute the script. 5. Test your scripts carefully. It is a good idea to use sample data to make sure the imports are working properly and data is going to the correct fields. Be sure to test the data on another machine to make sure the external scripts work. 6.
Chapter 4: Distributing your bundled solution The final step in preparing your bundled solution is creating an installation procedure. You should: 1 organize the files that end users need to use your solution 1 choose how you will distribute your solution, for example on a CD-ROM, the World Wide Web, or on floppy disks 1 provide end users with documentation for installing your solution This chapter covers the above, as well as information on running, updating, and recovering solution files.
4-2 FileMaker Pro Developer’s Guide Mac OS solution folder Windows solution folder runtime application runtime application bound solution files bound solution files FileMaker Extensions Data import filters Files for System Folder Items are moved into the end user’s System Folder Claris Spell-checking files 6 DLLs generated during binding System Spell-checking files and data and graphics import filters 4winsys For Windows 3.1 and Windows NT 3.
Distributing your bundled solution 4-3 The 4winsys folder If your solution will be used in Windows 3.1 or Windows NT 3.51, you must include the 4winsys folder and its contents with your solution. It contains files that are necessary for the “3-D” look and feel. When the runtime solution is first opened, the appropriate file will be copied to the \Windows\System folder, and the 4winsys folder will be deleted. When the solution is opened in Windows 95, Windows 98, or Windows NT 4.
4-4 FileMaker Pro Developer’s Guide In Windows 3.1, Windows for Workgroups 3.11, and Windows NT 3.51, items in the \Runtime Files\4winsys folder will be moved to the Windows\System directory when the runtime application is first opened. The empty folder is then deleted. On Windows 98, Windows 95, and Windows NT 4.0, the folder is not necessary and is automatically deleted if you have provided it in your solution folder. For more information, see “Installing Win32s” on page 4-9.
Distributing your bundled solution 4-5 Location on Developer Edition CD-ROM Preferred location on end user’s hard disk GIF graphic filter FileMaker Pro Binder\Runtime Files\System Solution folder\System Fmhpgl32.flt HPGL graphic filter FileMaker Pro Binder\Runtime Files\System Solution folder\System Fmmac32.flt MacPaint graphic filter FileMaker Pro Binder\Runtime Files\System Solution folder\System Fmpcx32.flt PCX graphic filter FileMaker Pro Binder\Runtime Files\System Solution folder\Syst
4-6 FileMaker Pro Developer’s Guide File or folder Description Location on Developer Edition CD-ROM Preferred location on end user’s hard disk Ctl3d32.dll Provides “3-D” interface for Windows 3.1 FileMaker Pro Binder\Runtime Files\System Solution folder\4winsys Ctl3d32.nt Provides “3-D” interface for Windows NT 3.51 FileMaker Pro Binder\Runtime Files\System Solution folder\4winsys Remember to distribute the Win32s 1.30c folder for your Windows 3.1 and Windows for Workgroups users.
Distributing your bundled solution 4-7 File or folder Description Location on Developer Edition CD-ROM Preferred location on end user’s hard disk Control Panels folder Drop items in that you want auto-installed FileMaker Pro Binder: Runtime Files: Files for System Folder: Solution Folder: Files for System Folder Claris Translators folder Contains graphics import filters FileMaker Pro Binder: Runtime Files: Files for System Folder: Claris Folder Solution Folder: Files for System Folder: Claris Fo
4-8 FileMaker Pro Developer’s Guide Compressing your solution If your runtime solution is small, you might consider a compression application rather than a custom installation application. To compress files, use a utility such as: 1 WinZip for Windows by Nico Mak Computing, Inc. (www.winzip.com) 1 StuffIt Deluxe for Mac OS (the StuffIt Expander decompression utility is available for Windows and Mac OS) by Aladdin Systems (www.aladdinsys.
Distributing your bundled solution 4-9 Installing Win32s To run solution files on Windows 3.1 and Windows for Workgroups 3.11, your end users must first install Win32s 1.30c. Disk copies of Win32s 1.30c are available from the FileMaker Pro 4.0 folder on the Developer Edition CD-ROM. Creating Win32s diskettes To create Win32s diskettes: 1. Format three 1.44 MB diskettes and name them Disk1, Disk2, and Disk3. 2. Drag the contents of the corresponding folders from the FileMaker Pro 4.
4-10 FileMaker Pro Developer’s Guide 4. Install Win32s. Instruct your end users to insert the Win32s Disk1. In the Program Manager, choose Run from the File menu and type a:\setup.exe from the Program Manager. Follow the Win32s setup instructions. 5. When the Win32s installation is complete, the FreeCell Setup dialog box appears. FileMaker, Inc. recommends To verify that the Win32s software has been installed correctly, your end users should install the game FreeCell, included with Win32s version 1.30c.
Distributing your bundled solution 4-11 Each time the runtime application is opened, it looks for the primary file that has been bound to it. If the primary file can’t be found, the end user is asked to locate the primary file. Caution your end users that they should not rename the primary or auxiliary solution files. If they do, relationships and external scripts may not work properly. They can rename the runtime application after it has been installed.
4-12 FileMaker Pro Developer’s Guide Recovering damaged files Power failures, hardware problems, or other factors can damage a FileMaker Pro file. If your solution becomes damaged, your end user needs to recover the damaged file. When the runtime application discovers a damaged file, a dialog box appears, telling the end user to contact the developer. Once you know which file is damaged, you can recover it; however, the Recover command does not appear in the File menu of the runtime application.
Distributing your bundled solution 4-13 Tell your end users to: 1. Recover the damaged solution file. 2. Open the recovered solution file. 3. Save a compressed copy using the Save a Copy As command. 4. Give the compressed file the same name as the original filename. For documentation ideas, see “Use custom Help script” on page 2-12 and “Documenting your files” on page 3-4.
Appendix A: Feature comparison—runtime application and FileMaker Pro Key differences between the FileMaker Pro runtime application and FileMaker Pro 4.0 include: 1 All the database design features have been removed or hidden in the runtime application. 1 The runtime application cannot access files over a network. 1 The runtime application cannot communicate with the FileMaker Web Companion. Hosting a database on the Web or communicating with a Java applet requires FileMaker Pro 4.0.
A-2 FileMaker Pro Developer’s Guide Menu Edit menu Mode menu Select menu Menu Item FileMaker Pro Runtime application Recover... • Ctrl-Shift in Windows; Option-Command in Mac OS Quit or Exit • • Undo • • Cut • • Copy • • Paste • • Paste Formatted Text (Windows) • Paste As... (Windows) • Some options aren’t available Clear • • Duplicate • Select All • • Paste Special • • Object (Windows) • • Spelling • • Preferences...
Feature comparison—runtime application and FileMaker Pro A-3 Menu Menu Item FileMaker Pro Runtime application Omit • • Omit Multiple... • • View as Form • • View as List • • Arrange menu All menu items • Format menu Font • • Size • • Style • • Align Text • • Line Spacing • • Text Color • • Text... • • Text Ruler • • ScriptMaker...
A-4 FileMaker Pro Developer’s Guide Runtime application-specific features There are some features that the runtime application supports that the FileMaker Pro 4.0 application does not, such as: 1 running solutions in Kiosk mode 1 specifying custom About, Help, and Script menu items When a runtime solution file with these options is opened in FileMaker Pro 4.0, the file behaves as if these binding options were not selected.
Feature comparison—runtime application and FileMaker Pro A-5 Additional limitations Other features have been removed from the runtime application. If your scripts contain any of the following items, the runtime application skips over them, and may not alert the end user. These items will not be executed.
Appendix B: About the TechInfo database The TechInfo database is a great resource for technical information about FileMaker, Inc. products. This FileMaker Pro database serves as a front-line resource for the company’s support technicians as they field customer inquiries. It collects Q&As, tips, FAQs, bug reports, update notes, press releases, templates, and a host of other material valuable for the support professional.
B-2 FileMaker Pro Developer’s Guide Keep the following search tips in mind: 1 If you don’t find an article in the title or description fields, try a keyword search in the main text field. 1 You can use the Find command in any layout. 1 The Refind command is handy for specifying a new or slightly different search. 1 Use the singular form, for example, “printer” instead of “printers.” 1 Try roots of words. For example: “summar” instead of “summaries” or “summary.” 1 Use generic terms.
About the TechInfo database B-3 Sample TechInfo article Below is a sample TechInfo article that has been edited for this Developer’s Guide. You can provide the backup script in the Script menu of your solution or create a button for your end users to back up their work. How To Automatically Back up Your Database Upon Exit If you are in need of an automated way to save back up copies of a FileMaker Pro 3.x or later database the following script will work well for you.
B-4 FileMaker Pro Developer’s Guide Other interesting TechInfo articles to search for: 1 Ten Steps to Designing and Building FileMaker Pro Database Systems 1 1 1 1 1 1 1 1 Relational Database Design 101 Corrupt Files: Recovery and How to Avoid It Removing Corrupt Records From a File Merging Two Databases While Updating Records Hierarchical Menus in FileMaker Pro 3.0 Troubleshooting Scripts: Hints and Tips How to Uninstall WIN32s From Your System FileMaker, Inc.
I-1 Index Numerics 3-character extension 2-14 4winsys folder described 4-3, 4-4 folder contents 4-3 A "About" layout described 1-2, 2-10 to 2-12 example file 2-11 legal requirements 1-12, 3-6 Accelerator keys 2-14 Access privileges, removing access to 2-10, 3-5 APIs described 1-1, 1-3 external function plug-ins 1-4 Java support 1-7 Applets, Java 1-7 Artwork Sampler database 1-14 ASCII characters 3-9 Auxiliary files binding 2-5 closing 3-2 described 2-3 opening 3-2 scripts for opening 3-2 updating 4-11 B
I-2 FileMaker Pro Developer’s Guide Distributing bundled solutions 4-1 DLLs 4-2 Documentation for runtime solutions 3-4 Help system 2-12 installation instructions 4-8 printed 2-13, 3-4 E EFP Documentation.pdf 1-5 End users license agreement 1-12 limiting access to solutions 2-9 Examples and Tools folder 1-14 Extensions, filename 2-14 to 2-16 External function plug-ins 1-4 to 1-6 F .
Index I-3 FileMaker Extensions folder 4-4 folder structure for solution 4-2 plug-in names 1-5 required solution files 4-3 runtime application requirements 1-11 Runtime Files folder structure 4-6 system requirements 1-11 Master access, removing 1-2, 2-9, 3-6 Menu bars, hiding 2-7 Menus, custom 1-2, 2-11 to 2-14 Monitors 3-7, 3-10 Movies, running cross-platform 3-14 N Naming runtime applications 2-4 Networks 1-11 O Opening solution files 3-2 P Parameters, external function 1-4 Password dialog box, suppress
I-4 FileMaker Pro Developer’s Guide specifying solution folder 2-17 testing 3-7 updating 2-20, 3-16 to 3-17, 4-11 Spell checking 4-5 Starting Binder application 2-3 Starting bundled solutions 4-11 Startup script 2-6, 2-8 Status bar, Windows 3-13 Support for Developer Edition 1-12 for end users 1-12 for external function plug-ins 1-5 System files 4-3 System requirements 1-9 T TechInfo database described B-1 navigating B-1 sample article B-3 searching B-1 Technical support for Developer Edition 1-12 for end
