Page 1 of 1

Best practice for updating older DayBack version

PostPosted: Tue Jul 23, 2019 1:35 pm
by Negan
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

Dave

Re: Best practice for updating older DayBack version

PostPosted: Tue Jul 23, 2019 2:17 pm
by kcembrey
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!

KC

Re: Best practice for updating older DayBack version

PostPosted: Wed Jul 24, 2019 10:29 am
by Negan
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.

Cheers!

Dave Wheelock