|
|
Posted by mark.rullo on 07/14/06 15:42
Posted in another group, hope this further explains what we need.
>
> You have not provided any background information or any functional details
> of the business model and rules. Without that others cannot meaningfully
> comment on a specific logical design.
>
> --
> Anith
I'll try and expand on the business requirements as requested.
Our goal in all of this is to have a facility wherin we can store
questions and the associated answers. We need to have multiple names
for these questions and answers over multiple Languages.
For each question ID (one question) we want to be able to ask it or
display it differently(n ways) (see above example).
The same requirement goes for each answer. We want to have multiple
"names" for one answer over multiple languages. For instance
QueAnsID = 1 | AnsNameID = 1 | LangID = 1(en) | "Yes"
QueAnsID = 1 | AnsNameID = 2 | LangID = 1(en) | "Y"
QueAnsID = 1 | AnsNameID = 1 | LangID = 2(fr) | "Oui"
QueAnsID = 1 | AnsNameID = 2 | LangID = 2(fr) | "O"
QueAnsID = 2 | AnsNameID = 3 | LangID = 1(en) | "No"
QueAnsID = 2 | AnsNameID = 4 | LangID = 1(en) | "N"
QueAnsID = 2 | AnsNameID = 3 | LangID = 2(fr) | "Non"
QueAnsID = 2 | AnsNameID = 4 | LangID = 2(fr) | "N"
This is so that when it comes together from the above example, we'd
pass in a groupID and a LanguageID into a proc and the result would be:
Do you have a dog in your appartment?
Yes
No
Or, if the group were different:
Do you have a dog in your house?
Y
N
I think the trick is not to put the LanguageID in the groupDetails
table so that the LangID can just be passed into the proc, and the
appropriate question / answer for that language is returned.
I hope this helps with the requirements.
Navigation:
[Reply to this message]
|