Product
Support
Everything Else
Only One Entry View Per Relation

As a general rule, you should not use two different entry forms in one Relation.

The two important reasons for this become obvious when you create a listing form of all the data in a Relation. In this examplel there are two entry form, one that contains "Duck" data and one that contains "Customer" data.

The first problem that arises is the creation of records containing blank Fields. When entering data on one form, a record is created for all the Fields in that Relation. the Fields that do not appear on the entry form will have no data stored in them.

The second problem results from what appears to be blank records. The "Customer" entry form may only have three Fields on it: "Name," "Address" and "Phone Number." If a Find First command is done on this form, the record will appear to be blank. Remember "Duck Name" and "Duck Breed" Fields do not appear on the "Customer" entry form. When you delete what appears to be a blank record, you will be deleting Daffy's record:

To fix this problem, create two Relations in this Collection, one for ducks and one for customers. The "Duck" entry form and "Customer" entry form should be in their corresponding Relation.