Scenario:
A Vacancy table containing fields like [salary], [manager] and [job title].
When a vacancy is filled, users either select or create an Employee record for the successful candidate from the Vacancy record.
Relationship: Vacancy N:1 Employee
(because a vacancy can only be filled by 1 employee (existing or new), but an employee can apply to multiple vacancies and change role internally)
Obviously, the aim is to avoid typing in [Job Title]/[Manager]/[Salary] again when creating a new Employee record from the Vacancy record.
An Employee sub-grid on the Vacancy form would be inadequate/poor design, as there would only ever be 1 staff taking on the job, so an Employee lookup makes more sense.
When field mapping from one table to the other, I couldn't find a way to make Vacancy the source and Employee the target.
The only direction was Employee to Vacancy, which is no use at all, since the Vacancy record comes first.
2) it only works when the source used to populate the related record is on the 1 side of a 1:N relationship, but not the other way around?
