One record in wedding info describes a single wedding.
One record in Ceremony describes the ceremony details for a single wedding?
One record in reception describes the reception details for a single wedding?
If so, you should have these relationships:
WeddingInfo::__pkWeddingID = Reception::_fkWeddingID
WeddingInfo::__pkWeddingID = Ceremony::_FkWeddingID
__pkweddingID should be defined as an auto-entered serial number.
If I have all that correctly interpreted, I'd add a fourth table: Locations. One record in this table would record the address and other details (NOT specific to anyone wedding) for a single location that could be used for the ceremony and/or the reception.
Link it like this:
Reception::_fkLocationID = ReceptionLocations::__pkLocationID
Ceremony::_fkLocationID = CeremonyLocations::__pkLocationID
ReceptionLocations and CeremonyLocations would be two different table occurrences that both have Locations as their data source table so that you do not have to enter address and other info twice for a location that can be used for both the ceremony and the reception.
If "table occurrence" and "data source table" are new concepts, you may want to take a look at this tutorial: Tutorial: What are Table Occurrences?