FileMaker Pro 10 and FileMaker Pro 10 Advanced Considerations and Issues

Backward Compatibility
Miscellaneous
Scripts
Save as PDF
Instant Web Publishing
Mac OS X
Windows
External Data Sources
Documentation Errata

1. Backward Compatibility
1.1. In FileMaker Pro 10, if a user navigates to a portal without selecting a specific portal row and without making an object active within a specific portal row, Get(PortalRowNumber) returns row 0 rather than row 1.
1.2. To add new custom menu items such as Saved Finds to menu sets created in versions prior to FileMaker Pro 10 Advanced, create a new custom menu and add the new menu item from the list ofstandard FileMaker menus in the Create Custom Menu dialog box.
1.3. When you execute the Halt Script script step with a “pre-event” script trigger, Halt Script cancels the original event, similar to when False is returned from an Exit Script script step.
1.4. If a file is hosted with an earlier version of FileMaker Pro or FileMaker Server, and a password change is required at next login, FileMaker Pro 10 clients will not be able to use the dialog to change the password. This issue does not occur when the file is hosted with FileMaker Pro 10 or FileMaker Server 10. Clients can still change passwords by choosing File menu > Change Password, as long as a password change is not required on next login.
2. Miscellaneous
2.1. If you have a printer saved in a script and the printer is named the same in Windows and in Mac OS X, when the script is run on the opposite platform and the printer is not the OS default it will print to the OS default instead of the printer in the script.
2.2. SMTP mail supports UTF-8 only.
2.3. User name will not be correctly encoded for some mail servers when the Email Address field in the SMTP server configuration is blank.
2.4. During an ODBC import, querying a SQL Server 2005 / 2008 table requires including the schema’s name in the query (i.e. schema.table) if it is not part of the schema being currently accessed.
2.5. The start of the week for find requests involving day names will always be based on the file’s locale (the regional/language settings for a file upon creation), even when the Use System Formats option is in effect.
2.6. Auto-complete only works in the last line of a multi-line field.
3. Scripts
3.1. If an external FileMaker file returns a set of related records when a “Go to related record” script step is executed, the sort order specified for the relationship to the external file will be ignored.
3.2. In Windows, if the functions Get(DocumentsPath) and Get(DesktopPath) are used to set a variable file or folder path, the string “file:” should be appended ahead of either function in order to be set properly. For example, create the following script: Set Variable [$test; Value: "file:" &
Get(DesktopPath) & "test.txt"].
3.3. “Run with full access” must be enabled for an entire script to completely execute if the script re-logins with an account that has no access to the current script.
4. Save as PDF
4.1. In Windows, when the Save Records As PDF script step is used with the Append option, the file attributes and permissions of the target PDF are reset to the system default.
4.2. In Mac OS X 10.4.11 (Tiger), opening a PDF file saved from FileMaker Pro in the Preview application with the option enabled to require a password on open and no password specified for printing will disable printing of this PDF file. A password prompt will display when attempting to print, however, it does not accept the password set for opening the file.
4.3. Some fonts cannot be saved out to PDF files from FileMaker Pro due to third party license restrictions. As a result, the PDF file may be blank.
4.4. Font fallback is not supported in saved PDF files from FileMaker Pro. An example of this is the tab control label (which only supports one font). If the font used doesn’t support all characters included in the tab control label, then the unsupported characters appear as out of range squares when saved as a PDF file even if they appear correctly on screen and when printed.
5. Instant Web Publishing
5.1. When using SMTP mail with Instant Web Publishing, you must specify the absolute path to any attached files in the Send Mail dialog (for example, filewin for Windows, filemac for the Mac OS). For FileMaker Server, place file attachments in the ../FileMaker Server/Data/Documents folder. For more information about file paths, see FileMaker Pro Help.
5.2. In Windows, to improve performance of an Instant Web Publishing or Custom Web Publishing solution, avoid using localhost in the URL by replacing it with the IP address, either 127.0.0.1 or the actual host IP. For example, change http://localhost/fmi/iwp to use http://127.0.0.1/fmi/iwp instead.
5.3. Formatting as a Drop-down calendar is not supported for timestamp fields in Instant Web Publishing.
Calendar icons and calendars will not appear in Edit and Find modes for this configuration.
5.4. Using the web browser’s “Back” or “Forward” navigation buttons within an Instant Web Publishing session is not supported or recommended because the results can be unpredictable.
5.5. Content in a web viewer may have unintended effects on Instant Web Publishing. Therefore you must test the websites you want to display within a web viewer. For example, certain web pages contain attributes that cause them to completely replace Instant Web Publishing in the web browser window.
6. Mac OS X
6.1. In the Mac OS, if you set up a print script step to output to print preview, the setting is not remembered when the script is run, it will instead print to the printer defined in the print script.
6.2. In the Mac OS, opening files containing transparent PICT images may cause the PICT images to no longer appear transparent in FileMaker Pro. Applying a transparent fill to the object may correct this problem.
6.3. In the Mac OS, SMTP mail does not support IPv6.
6.4. In the Mac OS, type-ahead is not supported for Asian characters in a drop-down list.
6.5. In the Mac OS, for some languages, you cannot access the Tutorial from the Learn It link on the Quick
Start Screen. Instead, choose Help menu > Product Documentation > Tutorial in order to open the
tutorial PDF.
7. Windows
7.1. In Windows, ScriptStatus() property of the ActiveX Application object returns 3 if a script is queued (triggered but not yet started).
7.2. In Windows, you cannot press Ctrl+Alt to force-apply an incompatible font from the formatting bar. Instead, use this key combination with Format menu > Font.
7.3. In Windows Vista with User Account Control enabled, running Setup.exe results in a UAC alert that refers to the program as Setxxxx.tmp. Confirming the alert will allow Setup.exe to run normally.
7.4. In Windows Vista, an object on a layout flashes as the document window is resized. You can fix this by enabling the option “Disable Desktop Composition” in the FileMaker Pro Application properties.
8. External Data Sources
For updates on supported ODBC data sources and drivers, see www.filemaker.com/support/technologies.
8.1. In Windows x64 editions, Oracle drivers will not accept login credentials from FileMaker Pro when attempting to connect to an Oracle data source if FileMaker Pro is installed into the default location: “Program Files (x86)” folder. For the Oracle drivers to work properly install FileMaker Pro into a directory that is not the “Program Files (x86)” directory. (Windows x64 has two “Program Files” directories, however, installation into the “Program Files” directory is disallowed.)
8.2. FileMaker Pro does not differentiate zero and NULL (empty) values in shadow fields. For example, changing a shadow field’s value from empty to “0″ and then refreshing the window will still display an empty field instead of “0.”
9. Documentation Errata
9.1. The following Control script steps no longer clear the last error condition: If, Else, Else If, End If, Loop, Exit Loop If, End Loop, Exit Script, and Halt Script.
9.2. FileMaker Pro 10 no longer requires deactivation when uninstalling the product.
9.3. The SetPrecision function returns inconsistent results in calculations involving small values. For example, for numbers with more than 16 decimal places, only 16 decimal places are returned.FileMaker Pro Help incorrectly states that constant numbers are left at the precision in which they were entered.
9.4. Some script step Help topics contain incorrect information about web-compatibility or server-side support. Here is the correct information:
9.4.1. The Insert Current User Name script step and Set Error Capture script step are supported in web publishing and in a FileMaker Server scheduled script.
9.4.2. The Open URL script step and Set Web Viewer script step are supported in web publishing but are not supported in a FileMaker Server scheduled script.
9.5. For the Install OnTimer Script script step, FileMaker Pro Help incorrectly states that the default interval is zero and you must specify a script name. The default interval is blank, not zero. You must specify a script, not a script name, because scripts can have the same name.
9.6. FileMaker Pro Help does not provide a complete list of the data returned by the Get(ApplicationVersion) function. Get(ApplicationVersion) returns: Pro (version) for FileMaker Pro, ProAdvanced (version) for FileMaker Pro Advanced, Runtime (version) for FileMaker Runtime, FileMaker Web Publishing (version) for FileMaker Web Client, Web Publishing Engine (version) for FileMaker Server Web Client, xDBC (version) for xDBC Client, and Server (version) for FileMaker Server.
9.7. In FileMaker Pro 10 for Windows, the keyboard shortcuts for increasing and decreasing text size have changed. You press Ctrl+Shift+> and Ctrl+Shift+< in order to increase or decrease to the next available size in the Format menu. You press Ctrl+Alt+Shift+> and Ctrl+Alt+Shift+< to increase or decrease text size by 1 point.
9.8. In addition to the column types and attributes listed in the ODBC and JDBC Guide, the SQL CREATE TABLE statement also supports the column types “Numeric”, “Double Precision” and “Float” and the column attribute “Unique”.
9.9. Get(HostIPAddress) returns only the IP address that the client used to connect to the host.