FileMaker Pro 10 and FileMaker Pro 10 Advanced late-breaking issues

[Ross MacLane]

FileMaker Pro 10 and FileMaker Pro 10 Advanced This document provides information about late-breaking and other issues in FileMaker Pro 10 and FileMaker Pro 10 Advanced.

Contents

1. Backward Compatibility
2. Miscellaneous
3. Scripts
4. Save as PDF
5. Instant Web Publishing
6. Mac OS X
7. Windows
8. External Data Sources
9. 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.

There is more, Please click here for more information.

There is also more here.

[Weetbicks]

Nice one, thanks for that Ross

QuagMire!

giggidy giggidy !!

[Norma_Snockurs]

Indeed. The general shake-out of the Get(LastError) function is interesting (and certainly one to be wary of in retaining backwards compatibility of your .fp7's).

[RichGags]

I added the Saved Find menu item to my custom menu, but its greyed out. I cant click it. What am I missing? Thanks!

Rich

[wlb_wtfd]

Thanks so much for this post. It was very helpful.

[conchology]

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.

bummer - thx for the info, now I know why I'm having the problem