There's some issues with the way you describe things. A value repeated in a field cannot be considered unique, for example. Nor is there any such thing as a parent or child table.
If this is a one to many thing, the one side ought to have a unique id (such as an auto number). This auto number is considered to be the PK (primary key) in that table. That PK is stored in the related (many side) table as a foreign key (this table should also have its own PK). You join the PK of the one side to the FK of the many side. You should not be using PK fields to hold meaningful data, which is what your authorization number.
Note that it is generally considered to be poor practice to use special characters (e.g. #) or spaces (save for underscore) in any object names.
Naming info:
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.