Exactly the same question was asked in the last thread. And in the overall "Monarch v12" thread. The workaround is to close the project, rename the database, then open the project and browse to the new database.
There will be a fix in a forthcoming patch. I don't know when that will be.