I have table A & B and their relationship is A->B as 1-to-many based on an unique ItemID in A
In fact, I know how many B should be there for 1 record of A
Say, 1 A can have 5 elements of B and each B has a different type ID to define its individual contents
For right now, because of the relationship definition I can only enforce one to many contraint in itemID so I can easily generate another record of B having an unique itemID in A exceeding the its total count of 5 and perhaps has another type ID which has already existed in its repertoire. I do not like this but I cannot find anyway to restrict this in the table definition
Is this the kind of thing that we should enforce in Form entry policy rather than in Table entry?