# 3970 ID For Unicode Collation Set Improperly in System Configuration Collations Table

---

Since the release 2.15 Build 1 (and unchanged with Build 2) we have the following problems:

1) Stored Procedures:

With ElevateDB Manager: If stored procedures that take parameter(s) of type VarChar are changed, the collation for the parameter field is completely lost (before changing: "UNI_CI", after changing: "_CI"). This happens even if only the SQL statement has been changed, and no changes have been made to the parameters. So everytime we try to save the procedure the message appears:

"ElevateDB error #700 ... The collation does not exist in the configuration EDBConfig".

When the collation is re-set to UNI_CI, the procedure can be saved. But when we look at the column properties the collation is again _CI, and on the next editing of the procedure the collation(s) must be set newly. Even the procedure does not work correctly.

2) Tables:

With ElevateDB Manager: If in an existing table an existing field of type VarChar is changed (for example, the length of the field), the collation for this field is completely lost (before changing: "UNI_CI", after changing: "_CI"). Before we recognized at all what (the heck) is going on, on saving the table always the message appears:

"ElevateDB error #700 ... The collation does not exist in the configuration EDBConfig".

When the collation is re-set to UNI_CI, the table can be saved. But when we look at the column properties the collation is again _CI.