Are you making changes to the user interface, the underlying data structure
Direct/FaceTime/Text - 781.223.8884
Both of them.
to the table schema, I can understand the schema change and I may need a script to update those data to new structure. ( It's the clarify to me and I can understanding the change and write the steps).
to the UI , there are a lot steps and config including the scripts in the system.
I don't know what the best way is?
and thanks your quick reply.
There is no one single best way.
You basically have two choices:
- redo the changes that were made in development, in the production system. Risk: something is missed and features fail
- make the development copy the new master and import all data from the production system: Risk:data is missed on the import, serial numbers are not updated to set the proper next value
Dpending on the scope of the changes one or the other will be best, but they both carry risk.
I vote for option Nº 2. Option Nº 1 is not scriptable, Nº 2 is.
Option 2 becomes easier too, if you use RefreshFM http//www.goya.com.au/refreshfm We designed it to do all the hard work for you so you can run your update process in advance and know that you've got a good outcome before you go live with the changes.
Let me know if you have any questions.
This is one of the biggest shortcomings of FileMaker development and one I hope they address soon! I would love to see a "Migrate" or "Sync" or "Import" or something to move the schema changes from one FileMaker file to another. Why this doesn't exist is beyond me and it really hapers complex ongoing development changes.