Best practice for updating older DayBack version

Notes on our latest calendar for FileMaker 13,: DayBack
Posts: 3
Joined: Wed Nov 15, 2017 2:45 pm
PostPosted: Tue Jul 23, 2019 1:35 pm
Hey guys and gals, just curious about what process you seedcoders would use to update a significantly outdated (10.14 in this case) version of DayBack. What's the most efficient way to jump to the latest version?

Many thanks, and keep up the awesome work

SeedCode Staff
SeedCode Staff
Posts: 347
Joined: Tue Nov 08, 2016 1:54 pm
PostPosted: Tue Jul 23, 2019 2:17 pm
Hi Dave,

This really depends on whether you linked or embedded DayBack, and the customizations you've made to the DayBack solution. There are really two options:

1. Apply the in-app updates, then apply any required script updates from build 10.15 to the latest.
2. Re-implement the latest version of DayBack into the solution, an replicate any customizations made.

The best choice really depends on how many customizations you've made, and whether or not you are confident you can replicate them in the solution. The script updates do take time, but they're very straight-forward. So, if you're not sure whether you can replicate all the customizations to the solution, it's probably best to go the normal updates route.

Hope that helps!

Posts: 3
Joined: Wed Nov 15, 2017 2:45 pm
PostPosted: Wed Jul 24, 2019 10:29 am
Hi KC,

Thanks for the reply, makes perfect sense. In this case, DayBack has been embedded, and moderately customized. I have used #1 as you described, and will continue to do so. The only unavoidable tedious aspect is updating the FileMaker scripts.


Dave Wheelock

Return to DayBack Calendar for FileMaker

Who is online

Users browsing this forum: No registered users and 2 guests

Follow us: