Safe to upgrade to 17 in middle of a project?

Hi everyone,

I'm in the middle of editing and grading a project and would like to upgrade from DRStudio 16 to 17 for some of the new features. I'm nervous to do this. Are there any risks I should know about?
Thanks in advance.
Simon

Basically wondering if I backup my Database, and Upgrade my Database, will I still be able to access the project I started in DR 16?

Thanks.

My personal preference would be to finish the project rather than live dangerously.

i live dangerously...

need to save current database,
restore under a new name
close backed up database after validateing it
and upgrade exisitng database
the very first v17.0 beta had issues with ACES, that was sorted in short order
i have kept v16 side by side on my machine after the ACES issue bit me, but have had zero reason to open it in months now
*note that keeping v16 and 17 alive is not supported, not recomended, and not a great idea unless you are comfortable sorting out any thing that goes bump in the night by yourself

the color tool in v17 are well worth the upgrade

stepping back to where you were with v16 is not a big deal - either uninstall 17 / reinstall 16 and use the v16 database, or in my case click on the v16 icon and use the v16 database

some stuff is broken by doing this (scopes have to be reset when going back to v17, nothing major), and it's not really worth keeping them side by side for long, chances are you will never need to turn back to v16

Thanks Robert and Dermot. All input appreciated.

I'm also of the living dangerously ilk.
I'll follow your protocol Dermot. Thanks very much for that.

cheers

A lot of folks are always "in the middle of a project".

I do find testing on a second machine invaluable as SOP, along with standard backup procedures.