A possible explanation for 'Name not Unique in this context' errors

By: Borland Staff

Abstract: The error, 'Name is not unique in this context' means there's already a component (field or otherwise) on the form with the same name.

Problem:
My app was working fine, when I went to add some fields into one of my
 tables.   When I try to add the fields using the field editor, I get an error
 message stating 'Name is not unique in this context'.

 What happened?

Solution:
The information in this document is relevant to all versions of C++Builder and Delphi.


The error,  'Name is not unique in this context' means there's already a component 
(field or otherwise) on the form with the same name.

One instance where this error can occur is if you have a form that is descended from another form.
If you create the field on the parent form, then try to explicitly add the field to the child
form as well, rather than inheriting it, this error can occur.





source: list serve

Server Response from: ETNASC04