Författare Ämne: Nyheter i FileMaker 10  (läst 8645 gånger)

0 medlemmar och 1 gäst tittar på detta ämne.

Utloggad Martin Norén

  • Administratör
  • Nykomling
  • Antal inlägg: 84
    • Visa profil
Nyheter i FileMaker 10
« skrivet: 9 januari, 2009, 12:12 »
En bra sammanställning med nyheter, varav många odokumenterade, finns sammanställda i FileMakers Knowledge Base:

http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/enduser/std_adp.php?p_faqid=7053

Intressant för den kalenderbitande utvecklaren är följande beteendeskillnader jämfört med tidigare funktioner:

Layout object tooltips
You can now use FileMaker Pro to add descriptive text that appears when customers move the pointer over layout objects in Browse or Find modes. Prior to FileMaker 10, this feature was only available in FileMaker Pro Advanced.

Scripting user interface improvements 
Use the Manage Scripts feature (formerly ScriptMaker) to display a default script you can use as a starting point for writing your own scripts, see whether individual script steps are supported in web publishing or in FileMaker Server schedules, and more. The Manage Scripts dialog box no longer opens in a maximized state when the FileMaker Pro window is maximized.

Removal of the "File Maintenance" feature
The File Maintenance features (compact and optimize) have been removed from the product and instead you should use 'Save a Copy Compacted' from the File menu as a better substitute.

In addition, the "optimize" functionality is always performed as part of the 'Save a Copy Compacted' feature.

Link to FileMaker Forum from the Help menu
A link has been added to the Help menu titled "Visit our Forum".

Suppress duplicate sharing errors on opening of multiple file solution
The same warning/error message is no longer displayed several times in a row just because one file causes the immediate opening of another file. This most frequently occurs with sharing errors like "FileMaker cannot share files because...."

Insertion of objects in the middle of the layout's object tab order
You are now able to insert objects in the midst of the existing tab order. You can enter the number corresponding to the desired position in the tab order for the selected object. If this causes a conflict with another object in the tab order, the intervening objects are automatically shifted in the tab order to accommodate this change. (Previously this would cause the two objects to swap in position.)

For example, if ten objects are already in the tab order (1, 2, 3.... 8, 9, 10) and you wish to make the current 9th object become the 3rd object in the tab order, you can accomplish this by simply entering "3" for the target object. The intervening objects 3 through 8 are automatically shifted to positions 4 through 9 in the tab order. Similarly, changing the object's ordering back to 9 causes the same intervening objects (now 4 through 9) to shift back down to 3 through 8 to both consume the released 3rd position and free up the 9th position again. This restores the prior ordering exactly.

No implicit commit before Replace/Relookup Field Contents operations
In FileMaker Pro 10, the Replace Field Contents and Relookup Field Contents commands and script steps will no longer exit the active field and commit data before performing the replace/
relookup.

For example, if you modify a field value and then try to perform a relookup on that field without committing the data, then the relookup search will be based on the old data rather than the modified data.

Additional common font sizes in font size menu; increase/decrease font size commands visible; improved toolbar font size menu
Point size 11 and 13 have been added to the font size menu and the "Increase/Decrease Size" commands are visible in the Size submenu. The additional point sizes are available via the toolbar font size menu as well as the relationships graph text note feature and the layout text formatting dialog.

The toolbar font size menu also shows custom font sizes and allows you to select the last custom size specified. Previously, this menu would just appear blank and not show anything for odd sizes.

Standard timestamp format and tab-delimited format in .log files
All created logs (Recover.log, Conversion.log, Import.log, ect.) use the tab-delimited format. In addition, the timestamp in all of the .log files use the universal timestamp format adopted in FileMaker Server 9, to make comparison of logs easier.

ODBC Import Error Code Change:
When importing from ODBC data source (executing SQL statement) and encountering an error, the system now returns the same error code as ESS does. However, it is different from the error code on FileMaker Pro 9 and earlier.

    Before: Get(LastError) returns 5, Get (LastODBCError) returns 42000
    Now: Get(LastError) returns 1408 and Get(LastODBCError) returns a textual ODBC error message. If there is no error message from the backend database management system and/or driver, Get(LastError) returns 1409, which is a rare case.

Do not clear LastError across script control steps
Script control steps (if, else, else if, end if, loop, exit loop, end loop, exit script, and halt script) have always cleared LastError. This had made it difficult to both test Get(LastError) and then act on it afterwards because the condition used to test it would clear it.

In FileMaker Pro 10, all script control steps never clear LastError any more. This means that it is now possible to have a script that tests Get(LastError) in an If statement and then use Get(LastError) in the following statement without having to save it in a variable first. This behavior is only available in this and newer versions of the FileMaker product family.

Script Debugger enhancements in FileMaker Pro Advanced
When a modal dialog comes up during execution of a script, the script debugger will show the current script and position. The indicator now remains on the pausing script step until the pause action is completed. Clicking the Step button at this paused point will now complete the pause action and advance to the next step. Renamed "Step" debugger action as "Step Over"

SQL Server Single Sign-on UI Change
In order for the FileMaker client to be able to authenticate to SQL Servers through a middleware server (either a FileMaker Pro host or FileMaker Server) the Kerberos Service Principal Name (SPN) needs to be specified. This string is part of the data source connection information, and is required for Single Sign-on (SSO) to work at all.

The Edit Data Source dialog for ODBC data source has been updated to include a new option to the authentication section. The new option appears after "Specify user name and password" and is called "Use Windows Authentication (Single Sign-on)". The option enables a new text entry field for the SPN (Service Principal Name).

Martin Norén | Square Moon | www.squaremoon.se | FileMaker 7/8/9/10/11/12 Certified Developer