Claris FileMaker tips, techniques, and news.
This is a two-part article tackling the challenge of converting and consolidating FileMaker Pro .fp3 and .fp5 file types to .fp7 and .fmp12. In part one, we cover the FileMaker conversion process. In part two, we cover the process of FileMaker File Consolidation. If you are already using FileMaker 12 or above, go on to part two.
Between the two parts, we will guide you through converting and consolidating a multi-file .fp5 solution while maintaining the functionality of your previous solution. And of course, you’ll be gaining all the latest FileMaker feature enhancements. Once you complete the conversion and consolidation process, no layouts will be visible to the end-users, scripts will be hidden, and your menu will be custom-designed to clean up your interface and enhance the user experience (e.g. Report Menu). The end result will be a consolidated, clean, single .fmp12 solution from what was once a multi-file .fp3, .fp5, or .fp7 system. (Depending on your consolidation design, you may actually have a few files, but it will still be greatly improved.)
While everyone has different needs, of the four options, we most often recommend going with the first option. We suggest this route because it costs the least long-term, carries the least amount of risk, and provides the most benefits. However, converting FileMaker Pro from .fp3 or .fp5 format to .fmp12+ can be a complex task that poses challenging problems.
Making the jump from FileMaker 3, 4, 5, 5.5, or 6 to FileMaker 7, 8, 8.5, 9, 10, 11, or 12 involves proper planning. Depending on the complexity of your FileMaker .fp5 system, this can take anywhere from a few days to a few weeks, depending on the number of files, scripts, layouts, relationships, and value lists in your solution.
We highly recommend these tools to effectively convert your files:
Obviously, this can really add up money-wise. If you’d like help, fill out our FileMaker Project Request and we can work with you to get you the best possible solution.
Before you start converting your files, you need to carefully map out your solution. Mapping involves knowing all your files in your current system, their primary relationships, and how you would like to arrange them in your new FileMaker system. This not only leads to better system architecture, but oftentimes, mapping out the files highlights files that are no longer used and can be eliminated.
To understand the main components of any system and guide the solution, we always create an Entity Relationship Diagram (ERD). The ERD becomes the cornerstone of the development process. While the average user can usually skip this part, you must be sure to know your solution to ensure the application is properly designed.
Next, you need to create a DDR in FileMaker 6 Developer. The DDR is a report of the entire system at the file level and helps determine whether to use the hub-and-spoke methodology or to rewrite the entire system. The DDR will be referenced throughout the conversion process. If you do not have FileMaker 6 Developer, this can be skipped, but be sure to know your solution so the application is properly designed.
Ensure all your files have the same full-access password. FileMaker 6 and prior are not case sensitive, while FileMaker 7 and higher versions are case sensitive.
Run your existing solution through MetadataMagic’s Developer Software. MetadataMagic will do three key things for you:
TIP: If your solution is in production and you don't want to do this on a live copy, take the latest backup and do this work and the remainder of the conversion from the backup.
Right now is a good time to eliminate/purge items no longer used rather than carrying around the luggage throughout the conversion. Identifying the relationships to purge is a top priority as we like to rename the table occurrences to a single naming convention. We recommend you run the solution through MetadataMagic or BaseElements each time you purge items to ensure you didn't create any errors and identify new items to purge. In a worst case scenario, you can easily go to a backup. Do the purging before the renaming to reduce your workload. Make sure you get approval before purging layouts and scripts as sometimes they are used by developers only.
TIP: When purging you should also look for items used in indirection, referencing an item by name instead of by the element's internal id before purging.
Read more about Indirection at Goyas' BaseElements, Unreferenced and Indirection.
Ensuring unique names in all files for relationships, layouts, valuelists, and scripts before converting is absolutely essential to a smooth conversion that includes file consolidation. Do this now, not later. It will save you hours of time. For very large solutions, the easiest thing to do is add a prefix to all the relationships, scripts, value lists, and layouts based on file name.
Read more about relationship naming in DB Services’ article, FileMaker Naming Conventions and Standards.
For relationships, we recommend using a standard convention such as adding a suffix to each relationship that has sorts and/or cascade create/delete rules (e.g. client__INVOICE__srt_cre_del).
TIP: Expect to review all Go to Related steps in scripts or on layouts after conversion. These will be found in the Conversion Issues Report.
Next, document all layouts visible to the user. This will help ensure you include navigation to the visible layouts either as part of the user interface or in custom menus.
TIP: Generate a list of duplicate layout names and only rename/add prefixes to duplicate layout names.
A good practice here is to generate a list of duplicate scripts and only rename/add prefixes to the duplicate script names. Next, document all scripts visible to the user. This will help ensure that any scripts in the current Scripts menu are included either in layouts or menus. Be sure to review the Scripts that are visible to end-users.
Tip: In the pre-FileMaker 7 days, each file was a single table. When you called a script in another file, FileMaker assumed you were now in the context of the file you just called. So, if you called an external file script and the first line was New Record Request, then in the consolidated file in .fp7 or .fmp12 format, you would be creating a new record based on where you are at and not in the external file in .fp5. For this same script to work appropriately in a consolidated file in .fp7 or .fmp12 format, you need to change the context of the script to have a Go To Layout to the appropriate context before the New Record Request.
MetadataMagic's Conversion Issue Report provides a great starting point for all occurrences of scripts called externally. The external script must have a Go To Layout call present at the beginning of the script. Also, scripts that call an external script and return must have a Go to Original Layout after executing the external script.
Again, ensure unique value list names in all files. A good practice is adding a prefix based on the file name/table to each value list. This will allow you to easily know what file the value list originated in the .fp5 format.
Update field names to a standard naming convention. We use lowerCamelCase, where key fields begin with an underscore, no spaces in field names, no non-SQL compatible field names, and all non user-editable fields and derived fields begin with 'z', etc.
Now that you’ve finished all of the steps above, it’s time to convert all files to FileMaker 7+. That said, we recommend you do the conversion in FileMaker 11 as early versions of FileMaker like version 7 handle file conversions differently and do not provide the copy and paste functions now available in FileMaker 8+.
Read the FileMaker's Knowledge-Based Article Converting older FileMaker Databases to the .fmp12 format. This article also includes FileMaker Trial Download Links that you will need to upgrade from the .fp5 format. Warning: It will be much easier to download and install the older versions on Windows vs Macs.
Are you looking to consolidate the files? We commonly use the Hub and Spoke method, to consolidate the files to the largest file to serve as the single.FMP12 file. The largest file of solution is typically based on the number of scripts, layouts, relationships. This will save you a lot of time.
Continue to Upgrading FileMaker Pro, Part 2 - File Consolidation.
Did you know we are an authorized reseller for Claris FileMaker Licensing?
Contact us to discuss upgrading your Claris FileMaker software.
Kevin is CEO and Business Project Manager for DB Services. He also a founding member of the FileMaker Partner Council and certified in FileMaker 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, and 8. Kevin is passionate about FileMaker as a custom application platform and is constantly on a mission to improve how he approaches each assignment.