When upgrading a CaseTalk Server database to version 4.00, the step that introduces the role-flags column can fail on databases where a 'flags' column is already present on the roles table (as a nullable column without a default). The upgrade tries to add the column unconditionally and stops with a duplicate-column error, leaving the column in an inconsistent state (nullable, no default) instead of the intended mandatory column with an empty-string default. Databases without a pre-existing flags column upgrade normally.