>>Hi everybody,
>>
>>I have a ProblemResolution table with 3 integer fields PK, FK1, FK2. In theory, a Problem may have multiple resolutions and vice versa. For now, I have them as 1 to 1.
>>
>>I'm thinking what would be the simplest and most intuitive interface for this table maintenance? Or should I probably combine maintenance of Problems, Resolutions and ProblemResolution in one form?
>>
>>Appreciate your valuable insights.
>>
>>Thanks in advance.
>
>I would make one form with 2 pages: Problems and Resolutions. Each page will have a grid (full list of records) and details container. Each details container will have another grid with child records from ProblemResolutions. In other words, functionality will be duplicated, but users will have an option to get there by 2 ways. It might happen you will be requested to make one of these grids read-only, probably 'Resolutions'.

I do not see how can I relate Problems with Resolutions, e.g. how can I build FK - FK table using this type of the interface.

Thanks again.