5 Replies Latest reply on Jul 29, 2015 9:13 AM by philmodjunk

    Move records from version 1 to version 2 after an update

    stuartreid

      Title

      Move records from version 1 to version 2 after an update

      Post

      I shipped version 1 of our filemaker database last January. It is a school solution and now has 250 students, 30 teachers etc etc.

      Soon I will have new version ready for the start of the school year in Aug/Sep. Have made a gazillion improvements and added a lot of stuff but was conscious not to delete fields. 

      As every developer produces updated versions, I expected this process to be simple and easily done by my client at the school. But, I can't find anything.

      I have written a script to go to a layout and export all the data from the layout's table. So far I've written script for 1 layout as a test but have 150 tables to deal with. So it can be done but it seems pedantic in this day and age.

      So that gets the data out of the old version into 150 files on the desktop - ouch !

      Now to get them into the new version.

      What I can find in my searching is a description of the old sneaker  net -- manually importing 150 files and matching them to the appropriate fields.

      This really breaks down when you consider the non-technical nature of our client and worse if we have to do this for every client. 

      I am positive that other developers have solved this so ... anyone have some suggestions before I dive in.

      Seems late in the game to discover this issue but, honestly, I assumed it was built in. We've written sports solutions (non-Filemaker_ where the data files where external to the app and so a new version just linked to the older data and that was it.