Marc Wielage wrote:He's not wrong.
Nobody is ever wrong for advising a user to consult reference materials. The question is whether it's helpful in every and all instances, any more than instructing all Premieres users who are questioning the forum narrowly on Resolve features that the only way they'll learn is to forget everything they know about Premiere and do as one person here, who's not a trainer, editor or a post-production professional, advises.
Marc Wielage wrote:In this case, the easiest way to back up is to export a DRP of the session (preferably on a daily basis, with an ongoing project).
Easy it may be, but in this case, there is appparently no backup. That's the situation which has be dealt with. Although to be fair, it's not altogether clear what the OP's problem actually is. If in fact she doesn't know how to use the project manager to open a project, that indeed would be a new low in user due diligence.
Marc Wielage wrote:A Resolve .db file is not intended to be moved or changed or renamed or copied directly by the user. Like it says in the manual, users need to do any session/database operations within the Project Manager. That includes backing up the Project Libraries, which you can very definitely restore with the Restore command.
I'm not sure where exactly it says that in the manual, but what you're supposed to do and what you may have to do are two different things. Some conditions are not correctable from the Project Manager. Dwaine himself routinely provides instructions for adding projects directly to the Projects folder -- manually, not through the Project Manager. And you can't "very definitely restore with the Restore command" if there's nothing to restore. Or the restore fails.
If the choice is between losing everything or manually altering the database with a simple copy and paste operation, what will you do? Tell the client the manual says you're not allowed?