Database errors replaces an internal error message that matches a selected text with a new error message displayed to the user.
Refrain from using it in new development since the text matched often is encountered in unexpected contexts where the user error message is not suitable. For example a foreign key name often matches errors in both Delete and Insert menu items, but the error message to the user should be completely different. Database errors are also not supported in all contexts an error might be triggered.
Strive to remove existing usage, and replace with actual error messages defined where they can occur, using for example ADMIN_ErrorMessage.