>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.
Maybe a "pivot table" where, for example, rows represent problems and columns represent solutions and may be useful. In this case checkboxes in cells will represent problem-solution connections.
But if there are large numbers of entities this will probably need dynamic generation of column set and order.
/A new technology turns into completely outdated stuff before you have a time to read "Getting Started..." section.
/If there are some "system programmers" then others are unsystematic.
