Justine,
As I have explained in the previous thread, your table design needs to
have one field for each data entity, and the data entered into this
field as separate records. In your current design, you are
distinguishing data according to which table it is in, or according to
which field it is in, rather than according to which record it is in. I
tried to express this diplomatically before, but now I will try the
blunt approach - WRONG!! If, for example, the data you are recording
involves the entry of multiple Codes for each Application, then you need
a table where each of these "selections" is a separate *record*. The
fields might be:
AppCodeID (PK)
AppID (FK to Applications table)
Code
... (although I suspect it won't be as simple as that, as there is the
other stuff about Regions and such like to take into account)
But anyway, I suggest you forget the form and such like at the moment,
and get the tables normalised.

Signature
Steve Schapel, Microsoft Access MVP
> Hello,
>
[quoted text clipped - 85 lines]
> Thank you kindly,
> Justine