P
Phil
This is an approximation of my problem. Please don't get hung up on how
I am doing it. This is just an easy way to explain it.
I have two tables. One is SalesDetail, the other is ItemDetail. Items
have two numbers, SpecificID, and GeneralID. SpecificID is one for one,
each item in ItemDetail gets it's own SpecificID. The items come in
different Colors, each with it's own SpecificID, but each Item
regardless of color, has the same GeneralId. The same thing in five
different colors, will have five different SPECIFICIDs, and ONE common
generaID.
The SalesDetail File only tracks the generalID. We have made some, (and
will again) changes to the data in the ItemDetail file, and need to
carry those through to the SalesDetail file. Those changes are uniform
throughout each general ID. A change to One specificId was made to ALL
specificIDs with the same GeneralID. For Instance, we changed the name
of the item.
Here is the problem. I can create an update query, based on a query of
the ItemDetail table, which will result in a hit for each color on the
ItemDetail table, everytime it matches up to a generalID between the two
tables. This seems to work, in that when I am done, the SalesDetail
file is updated and looks correct. The problem is, with as many as 48
colors per GeneralID, it takes FOREVER.
Since the relevant data for everything under a generalID is the same, I
can make the query of ItemDetail unique query, to give me the data Once
for each GeneralID. When I do this to the underlying query, the update
query becomes nonupdateable, and fails. I am updating directly to the
table, and am not changing anythign on the fuinal query itself.
However, simply because the source query is unique, I can not use that
information to update something else?
What am I missing?
Thanx
I am doing it. This is just an easy way to explain it.
I have two tables. One is SalesDetail, the other is ItemDetail. Items
have two numbers, SpecificID, and GeneralID. SpecificID is one for one,
each item in ItemDetail gets it's own SpecificID. The items come in
different Colors, each with it's own SpecificID, but each Item
regardless of color, has the same GeneralId. The same thing in five
different colors, will have five different SPECIFICIDs, and ONE common
generaID.
The SalesDetail File only tracks the generalID. We have made some, (and
will again) changes to the data in the ItemDetail file, and need to
carry those through to the SalesDetail file. Those changes are uniform
throughout each general ID. A change to One specificId was made to ALL
specificIDs with the same GeneralID. For Instance, we changed the name
of the item.
Here is the problem. I can create an update query, based on a query of
the ItemDetail table, which will result in a hit for each color on the
ItemDetail table, everytime it matches up to a generalID between the two
tables. This seems to work, in that when I am done, the SalesDetail
file is updated and looks correct. The problem is, with as many as 48
colors per GeneralID, it takes FOREVER.
Since the relevant data for everything under a generalID is the same, I
can make the query of ItemDetail unique query, to give me the data Once
for each GeneralID. When I do this to the underlying query, the update
query becomes nonupdateable, and fails. I am updating directly to the
table, and am not changing anythign on the fuinal query itself.
However, simply because the source query is unique, I can not use that
information to update something else?
What am I missing?
Thanx