I moved development of a solution which was started in 13 over to 14. No Plugins, no external databases but separation model applied. Started modification of existing layouts and introduction of new v14 features last week. Haven't experienced any problems yet. This solution is not close to production, so it's just a tester for the moment. I am developing this one local, not on server which is still version 13 for safety reasons.
I reworked an older solution to test V14, no problems.
Theoretically, the best would be to begin from scratch, using the new methods for button bars etc. - but having to do that with every new version of FM, the ones who have to pay for that will hold back - and FM gets a bad reputation..
Estimate the time it would take you to do both approaches to attain the same end product and choose the one that makes the best business sense.
14 does offer some nice new features but 14 is completely backwards compatible
be cautious with the new FMP14 features and read the "Daily News"
can I simply update the layouts in a database that was created in FM13 or should I build a new database from the ground up FM14 and import all the necessary things from FM13?
I wouldn't rebuild the layouts from scratch. Some changes with stiles and theme will be necessary but thanks to CSS, you do this once for one kind of a field.
Once more, some change of behavior appear with FMP14.
Of course the layouts will be from scratch but built on the same database that was built in 13.
FileMaker moves forward in a manner that makes older stuff work with the newer. But there are times when designing a new layout is better than using an old one.
First try each of the new layout options offered when you create a new layout and you will see that the engineers have decided to provide device specific layouts with special features rather than one layout that you have to modifiy.
Take some time to design a new layout with one for PC, one for iPad and one for iPhone. Each has its own stuff and that has been designed to work on those devices. Don't drag fields and buttons from old layouts but use the design tools within 14 to add fields and buttons, etc. See if there is any benefit to you. I've noticed a real difference in using an iPad layout on a iPad and on a Windows laptop. Using the PC layout options works better. So I now have something like:
[FORM] Address PC
[FORM] Address iPad
[FORM] Address iPhone
I have decided to move forward with 14 only and not have to design 6 more layouts for 12 and 13.
By isolating layouts to devices I don't try to make a layout designed for a 27" iMac work on an iPhone. Won't happen. It does make me think, "What will someone using an iPhone need that is different from using that 27" monitor?"
You should be fine with your FM13 file.
I never use v 1.0 of anything except for testing.
In most cases we start now building layouts with "Touch" styles which look good on desktop as well. I this way, we do not need to design a second version for the iPad. It saves a lot of time. With older layouts, we duplicate the layout, use the duplicated layout as guide and redesign the original layout with ne styles. When finished, we delete the duplicated "guide" layout.
And miss the excitement?. No way .
The excitement of receiving 38 phone calls a day from angry clients is something I slowly began to appreciate less and less
How boring , oder ...?
... Must show more confidence in version 1.0