Defining table relations in fields
In our requirements described previously, we specified that the program needs to be able to specify the customer and the vendor information. The customer and vendor information must be valid, or else it really defeats the whole purpose of keeping track of the appropriate information.
To ensure that the user enters the relevant customer, we will need the user to be able to select from an existing list of customers that's already defined in the Customer table. In order to enforce this, we will need to define the table relationships to the master table data or set up tables within each field.
Go back to the Table Designer screen for our Table 50000 and click on the Customer No. row. Then, navigate to View | Properties.
The table relationship we're looking for will be zero to many. So a customer can occur zero times or more on the
Complaint Headertable and theComplaint Headertable can have none or one occurrence of a customer number.
Click on the AssistEdit...
