D
dlerh
My client is used to seeing data a certain way, and I can not seem to sway
her. I'm trying to normalize her database, and we're making pretty good
headway, but I have hit one particular snag that I can't seem to get around.
She's the librarian for a company's manuals, and she has to track full
manual revisions as well as temporary revisions. Apparently, a vendor might
publish 1 to 20 (or more) temporary revisions to different chapters of a
manual before they ever update the whole thing. While RevNum and RevDate
properly belong to tblManual, TempRevNum and TempRevDate belong in a seperate
table.
Here's the problem:
She wants the dynaset describing her manuals to include RevNum and RevDate
(easy enough), as well as ALL TemRevNum. Currently, she is WIPING OUT DATA,
and manually typing in something like this: "16-22, 44, 46a". Since she is
the client, and therefore right, I'm struggling with how to produce an
expression that concatenates every possible instance of a matching record,
and even accounts for lowest and highest value for consecutive numbers...
Is this even worth pursuing, or should I just give up? Should I tell her to
keep doing this the way she's doing it and try to work around her? Maybe I
should walk out in a huff and tell her, "It's a relational thing; you
wouldn't understand!" Am I making too much of this? Is there an easier
solution that I'm missing?
You guys are the best, so if you got nothing, I got nothing.
Thnx!
Dale
her. I'm trying to normalize her database, and we're making pretty good
headway, but I have hit one particular snag that I can't seem to get around.
She's the librarian for a company's manuals, and she has to track full
manual revisions as well as temporary revisions. Apparently, a vendor might
publish 1 to 20 (or more) temporary revisions to different chapters of a
manual before they ever update the whole thing. While RevNum and RevDate
properly belong to tblManual, TempRevNum and TempRevDate belong in a seperate
table.
Here's the problem:
She wants the dynaset describing her manuals to include RevNum and RevDate
(easy enough), as well as ALL TemRevNum. Currently, she is WIPING OUT DATA,
and manually typing in something like this: "16-22, 44, 46a". Since she is
the client, and therefore right, I'm struggling with how to produce an
expression that concatenates every possible instance of a matching record,
and even accounts for lowest and highest value for consecutive numbers...
Is this even worth pursuing, or should I just give up? Should I tell her to
keep doing this the way she's doing it and try to work around her? Maybe I
should walk out in a huff and tell her, "It's a relational thing; you
wouldn't understand!" Am I making too much of this? Is there an easier
solution that I'm missing?
You guys are the best, so if you got nothing, I got nothing.
Thnx!
Dale