M
Maury Markowitz
I have a table that includes details for a large number of stocks and
bonds. Many of the columns in the table store data for only one of or
the other of these classes (ie, dividends vs coupons) and is optional
in any case. I would very much like to remove these columns from the
main table and move to a more normalized data representation.
Doing so, however, can greatly increase the complexity of dealing with
that data in Access. Or maybe I'm just not doing it right. Ideally I
would like to use a view that joins the data back together into an
analog of its original presentation, and use that view in the few
forms where this data appears.
However, I'm not sure if this works - what happens if there is no row
in the optional table? Will Access handle these cases? I would really
like to avoid creating and deleting these rows if possible.
Subforms seem like a potential solution as well. However, I've always
found them difficult to work with. Is this the way to solve this
anyway?
Maury
bonds. Many of the columns in the table store data for only one of or
the other of these classes (ie, dividends vs coupons) and is optional
in any case. I would very much like to remove these columns from the
main table and move to a more normalized data representation.
Doing so, however, can greatly increase the complexity of dealing with
that data in Access. Or maybe I'm just not doing it right. Ideally I
would like to use a view that joins the data back together into an
analog of its original presentation, and use that view in the few
forms where this data appears.
However, I'm not sure if this works - what happens if there is no row
in the optional table? Will Access handle these cases? I would really
like to avoid creating and deleting these rows if possible.
Subforms seem like a potential solution as well. However, I've always
found them difficult to work with. Is this the way to solve this
anyway?
Maury