FileMaker Pro 12 Updates Themes and Layout Capabilities
FileMaker Pro 12, the database’s first integer-level update in a year and a half, offers little change in the way data is managed, stored, or structured. Instead, as Mark Anbinder discussed in his coverage of the update’s release (see “FileMaker 12 Adds Power, Clarity, and Free iOS Apps,” 4 April 2012), the focus is on display, presentation, and appearance. FileMaker’s Web site claims that this latest version offers “stunning” and “eye-catching” database design tools, and while this is clearly advertising hyperbole (it’s still a database!), FileMaker Pro 12 does improve significantly on earlier versions’
New Layout Tools — The primary enhancement that FileMaker Pro 12 brings is themes. Earlier versions included preset designs for new layouts, but they were riddled with problems, not least the fact that they were often garishly coloured and quite puzzlingly unattractive — some even looked like they could easily have been designed by a seven-year-old with a crayon. But even if you decided that you really, really liked the orange and yellow of Brick Screen, for example, the colour scheme of a layout created using that style applied only to fields added during the creation of the layout. Fields added afterwards had to be styled manually — colour, typeface, type style all
reverted to FileMaker’s defaults.
But this, mercifully, has changed. The 40 new themes are generally less gaudy and tacky than previous styles; the Retro theme is reminiscent of one of the skins available in Claris Organizer, which was sold to Palm when Claris became FileMaker, Inc. (“Claris Organizer Reincarnated as PalmPilot MacPac,” 11 May 1998). And the Wave theme would probably look quite at home on a Windows 7 desktop, which you may or may not feel is a good thing.
FileMaker Pro 12’s layouts are now much more tightly linked to their source themes. New fields added to layouts after their initial setup automatically inherit the styling of that layout’s theme. And themes can be switched after the fact — if the Wave theme really does remind you too much of Windows, then a quick trip to the Layouts menu’s Change Theme command will change the entire layout’s theme to something less jarring.
Refining elements within a layout has also been improved in FileMaker Pro 12. Perhaps the most important change has been to the way in which layout objects are selected. In previous versions, objects had to be enclosed completely by the selection area, but now the selection area merely has to overlap the objects you want to select. This is a long-overdue standardisation, but I have a suspicion that it might initially confuse veteran FileMaker designers used to the old approach.
Once layout elements have been selected, they can be styled much more extensively than had previously been possible. Gone are the dated dither patterns that somehow clung to life through FileMaker Pro 11; in their place come colour gradients for fields and buttons. Corners can be rounded to a specified radius; if a number of buttons are butted up against each other, for example, in a horizontal list, then rounding off the left corners of the left-most button, and the right buttons of the right-most object, can create a modern-looking style. Objects can be given different styles for different states, so that the currently active text input field might have a stand-out background colour, while a script-triggering button could be styled to
change colour when moused over, and again when clicked.
FileMaker Pro 12’s layouts are a decided improvement over the psychedelic mistakes of earlier versions’ colour schemes, but they might not be to everybody’s tastes. It’s a shame, then, that there appears to be no way for developers and designers to create their own themes, or even to save modifications to existing themes.
Five of the new themes, including the Windows-esque Wave, have companion themes with the word “Touch” added to their names. Clearly the good people at FileMaker agreed with my assessment of FileMaker Go and the constraints placed upon FileMaker Pro designers by the small screen size of the iPhone (see “FileMaker Go Brings FileMaker Databases to iOS,” 9 February 2012). At any rate, these five Touch themes are designed specifically to accommodate the smaller screens of iOS devices running FileMaker Go. More on that later.
File Formats — Long-time FileMaker developers will remember — indeed, many likely still wake at night in cold sweats from the nightmares — the traumatic experience that was the 2004 leap from version 6 to version 7 (see “FileMaker Pro 7: Can You Say Paradigm Shift?,” 15 March 2004). File schemata broke, quite badly in some cases, and an entire industry sprang up around the conversion from Old FileMaker to New FileMaker. But eventually things settled down, and since 2004, the .fp7 file extension has been a reassuring constant in FileMaker developers’ lives, a sign that everything is safe and comfortable.
The transition from FileMaker Pro 6 to 7 was, for many database developers, a growing pain that involved extensive retooling of databases constructed around kludges and workarounds to accommodate the fact that, before version 7, FileMaker Pro was not an actual, real, honest relational database. In an irony that failed to amuse many developers, the transition to a relational architecture broke — in some cases shattered — the data structures of many databases. But they were rebuilt, and have remained sturdy, robust little stores of information ever since.
The bad news for FileMaker developers, then, is that FileMaker Pro 12 brings a new file format, as evidenced by the new extension: .fmp12. The good news is that it won’t be accompanied by the same gnashing of teeth and rending of garments. That’s because the fundamental file structures of existing databases will not require any updating — no rebuilding of databases, no re-configuring of tables and relationships, no breaking of files. Updating a .fp7 file is simply a question of opening it in FileMaker Pro 12. According to the dialog that appears, “after conversion it will only be compatible with FileMaker 12 or later supported versions.” The dialog also offers an option to rename the old file; if this option isn’t selected,
a Name Converted File dialog opens to enable the user to save the converted file, leaving the original untouched.
The new file format is necessary to support the layout themes that are the marquee feature of FileMaker Pro 12, and it also enables an enhancement to the capabilities of container fields in FileMaker Pro databases. In FileMaker Pro 12, .mp3 audio files can be played from within containers, with the option of the audio playing automatically. Similarly, according to FileMaker’s Web site, PDF files can be navigated directly within a container, although the container field will need to be made large enough in
a layout for its content to be viewed easily.
The contents of container fields are now, more than ever, kept at arm’s length from the database itself — a database designer now has the option of either including the contents within the database file or simply placing a reference in the field to externally stored data. The trade-off is that data in container fields is still not searchable, and is increasingly unlikely to be made searchable in future releases.
Going Mobile — As I discussed in “FileMaker Go Brings FileMaker Databases to iOS” (9 February 2012), FileMaker, Inc. offers iPhone- and iPad-based mobile FileMaker clients in the shape of FileMaker Go. The $19.99 iPhone app is a fine and useful piece of software; the iPad counterpart is probably every bit as good, but its $39.99 price tag deterred me from trying it out. On the plus side, both apps have been updated and made free. On the down side, they work only with .fmp12 documents. And here is found the key to FileMaker, Inc.’s new philosophy with regard to their mobile applications.
Like its predecessor, FileMaker Go 12 is a capable FileMaker client, but it cannot create new databases; nor can it modify layouts, scripts, or data schemata. This limitation makes it an excellent companion to FileMaker Pro, but renders it effectively useless to anyone who does not already run FileMaker Pro on a desktop computer. FileMaker, Inc. appears to have realised that FileMaker Go is better and more properly considered a part of a larger FileMaker implementation, and so they have decided to give FileMaker Go away as a means of promoting sales of FileMaker Pro. As a result, the new FileMaker Go 12 brings little new to the iOS world, but will likely help in the
purchasing decisions of users of FileMaker Pro 11 who are considering upgrading but balking at numerous purchases of the old $39.99 version. And it certainly sweetens the deal for potential new users of the FileMaker product line. Happily for users of FileMaker Pro 11 who may still want them, the original FileMaker Go apps are still available from the App Store, at their original, high prices.
Sharing and Serving — FileMaker databases are designed to be shared, and this is where the new .fmp12 file format becomes a problem. FileMaker Pro 12 can share databases only in the new file format, and only FileMaker Pro 12 and FileMaker Go 12 can open those databases. If you want to upgrade, you’ll need to be aware that interoperability could easily be compromised — if you update one computer on a network to FileMaker Pro 12, then all the other computers need updating if they are to share databases. And if you’re tempted to try out the new free iOS apps, then you’ll need to be running FileMaker Pro 12 on your desktop computer or server.
The good news, then, is that both FileMaker Pro 11 and FileMaker Pro 12 can coexist on the same computer at the same time, each happily running its own databases. The bad news is that only one of them can share databases over the network at any given time. Given just how screamingly useful FileMaker Network Sharing can be in a small-office environment, with the FileMaker Pro client software doing double duty as a database server, it is disappointing that only one version can activate Network Sharing on any single computer. As a workaround, you’d need to set up one machine to share FileMaker Pro 11 databases and another one to share FileMaker Pro 12 databases.
While this complication does, to a degree, bifurcate the FileMaker universe, it can also be seen as a helpful step on the upgrade path. FileMaker, Inc. clearly wants us to upgrade, as is illustrated by the free iOS apps, but the fact that both FileMaker Pro 12 and earlier versions can be run at the same time should make the upgrade process substantially less painful than the rude blunt-force shock that was the jump from version 6 to version 7.
Should You Buy It? — While the new templates that are the centrepiece of FileMaker Pro 12 are pleasant to look at, and themes are likely to lead to fewer databases that look like they were designed under the influence of exotic recreational pharmaceuticals, there are few standout features of the new version of FileMaker Pro that make it a compelling upgrade.
Users of FileMaker Pro who have functional installations and databases that meet their existing needs will find little in version 12 to make this upgrade essential. Developers who produce FileMaker Pro solutions will want to keep both versions on their computers for the time being. Many of their existing clients’ needs will continue to be met quite splendidly by earlier versions, but new customers will likely be new users of FileMaker Pro and will start fresh with FileMaker Pro 12.
The tricky questions will be asked by small businesses looking to expand their in-office FileMaker solution to include a mobile dimension. Staying at FileMaker Pro 11 or earlier is, of course, free, but every iPhone with FileMaker Go represents an additional $19.99 cost, while each iPad costs an additional $39.99. With an upgrade to FileMaker Pro 12 starting at $179, upgrading could quickly become more cost-effective than buying multiple copies of FileMaker Go.
Certainly, FileMaker Pro will retain its position as the dominant desktop database development option of choice for many, and the fact that incorporating iOS devices into a FileMaker solution is now both free and easy to implement elegantly makes the entire FileMaker ecosystem a more attractive option for businesses that need a mobile solution. But FileMaker Pro is already a mature and robust platform, leaving the company with the challenge of trying to find new features that warrant a full integer-level upgrade. The design features of FileMaker Pro 12 are certainly attractive, in multiple ways, but unless the designs of your current databases leave you wanting to pluck out your eyeballs, it’s hard for me to recommend an upgrade
unless you’re also looking at needing to purchase numerous copies of FileMaker Go 11 for your existing systems.
FileMaker emphasizes the interface changes. They are important, and perhaps the most immediately obvious.
But under the hood there are a LOT of very significant improvements to this powerful and versatile application. Document management and ExecuteSQL are two one of these new features.
I suggest that you read the "What's New in FileMaker 12" section of FileMaker help. People who aren't regular FileMaker users may need some further help to understand the implications and practical uses of these changes.
I know - you could write a book! (With the help of an experienced developer...)
Two quick notes to add:
Version 9 users of FileMaker have an incentive to upgrade, as Filemaker, Inc., is temporarily offering an upgrade path from FileMaker Pro 9 that ends in September 2012, as I recall. Without taking advantage of the "upgrade" being offered, users of version 9 will have to buy full replacement versions of FileMaker Pro.
There are new liabilities to Filemaker 12 to mention for those that create runtime solutions using Filemaker Pro Advanced. Be aware that FileMaker is apparently following Apple's forced obsolescence model as FileMaker Pro 12 will only run on Mac OS 6.x (Snow Leopard), and OS 7.x (Lion), and that includes Mac "runtime" database solutions. On the Windows side, version 12 runtime databases will function fine under the well seasoned ten year old Microsoft Windows XP, as will the full version of FileMaker 12, so this appears to be an arbitrary decision of Filemaker to limit operating system compatibility on the Mac.
I'm a newbie Filemaker user, at present on version 11 (the Japanese version). I have a problem with garbled Japanese characters. Does anyone here have any knowledge of such issues?
More details: I bought Filemaker to import a Delicious Library database and add extra fields to it, and provide access to the database on iPads by using Filemaker Go. Unfortunately, Filemaker is unable to import any of the Japanese-language items without garbling the characters. To confirm that this isn't an issue with Delicious Library's export, I tried importing the same DL exported file into Bookpedia; that worked fine. So it seems to me that there has to be a problem either in Filemaker itself or in the way I have the settings. I'll happily pay for an upgrade if that's likely to improve things, but I haven't seen any mentions of this kind of problem.
Apologies if this kind of post isn't appropriate here; if everyone ignores it, I'll get the message!
There are several FileMaker Pro specific forums filled with genial and smart users who live and breathe for the opportunity to resolve a FileMaker conundrum.
Your best option is likely to post your query on one of those sites.