Jump to content
Salesforce and other SMB Solutions are coming soon. ×

From File MP 7 to FMP 12


Recommended Posts

Do you mean database files that are in .fp7 format, or do you mean databases that were designed in FileMaker Pro version 7?


(FileMaker 7, FileMaker 8, FileMaker 8.5, FileMaker 9, FileMaker 10, and FileMaker 11 all used the same .fp7 file format; a .fp7 file could have been designed and updated and kept current up through FileMaker 11 by whoever developed it, or it could have been designed in FileMaker 7 and lack any advancements and features created in the versions that came out since then)



Short answer: select all the .fp7 files of your database and DRAG them on top of the FileMaker 12 application icon; they will be mass-converted, with the original .fp7 files remaining and new converted .fmp12 files generated by the drag-and-drop process. They are now converted.


Long answer: Same as the short answer but then you need to open each one and stare at the scripting and architecture. You may wish to improve on older ways of doing things. FileMaker 8 gave us $Variables — if your FileMaker 7 file is chock-full of global fields used to hold temporary parameters you may wish to discard them in favor of $Variables. FileMaker 8.5 gave us web viewers — if your FileMaker 7 file opens URLs up in external web browsers, and it would be more convenient to display them directly on-screen you might wish to make use of web viewers. FileMaker 9 gave us conditional formatting — if your FileMaker 7 database has complex and cumbersome calculation graphics to change the colors and appearances of things based on field values, you may wish to rip that out and use the easier conditional formatting available now. FileMaker 10 gave us script triggers — if your FileMaker 7 database relied on 3rd party plugins such as ZippScript to "make things happen", to fire off scripts during data entry processes or something, you may wish to convert these routines to native FileMaker script triggers. FileMaker 11 gave us intrinsic charting — if your FileMaker 7 database used home-grown calculated container fields and other hacks to do charting, or exported to Excel to produce charts, you may wish to take advantage of built-in charting. And FileMaker 12 gives us the opportunity to store container field contents in associated folders external to the database itself, and gives fancy layout formatting options with gradients and themes and whatnot. If your FileMaker 7 database made use of SuperContainer or is clogged with lots of files stored in container fields, you may wish to convert to native external storage for container fields, and if your layouts look kind of 1991-ish with patterned backgrounds and objects, you may wish to redo them with FileMaker 12's themes and gradients.


and etc.

Link to comment
Share on other sites

This thread is quite old. Please start a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

Terms of Use