Hi Leo,

The easiest fix, given that you most likely don't care about the EHR Compliance module's data on your local system, would be to simply drop that schema manually from the database. That should allow the upgrade to proceed.

We try hard to avoid the need for these kinds of manual database fixup, but sometimes dev machines, especially those that aren't syncing and building regularly, can get into a bad state as we consolidate SQL upgrade scripts between versions.

Let us know if you need any help with the manual database manipulation.

Thanks,
Josh