If you are developing your own schema and creating record types without using packages, you can rename all field, action, state, and record names. However, changing these names might affect existing references to names in hooks, scripts, and queries.
A schema cannot include a Perl and a VBScript hook with the same name. If you attempt to create such hooks, the attempt fails. If you add a hook with the same name as an existing hook, restart the Designer and delete the new script.
A schema cannot have a field or record type name that is the same as a variable or constant name in a hook or script. You cannot declare in a hook a constant or variable whose name is the same as an existing field name or record name without causing errors. For example, you cannot name a variable status if you also have a record type named status.
Names cannot be the same as any reserved keywords for the database, prohibited by Rational ClearQuest interfaces (for example, Date), or contain any characters that are not valid.