C
C. Walters
Hi folks,
I have to design a table or tables to contain the
following type of info:
OrgNbr
OrgName
SubOrg1
SubOrg2
SubOrg3
SubOrg4
SubOrg5
Each Org can have multiple SubOrgs so I would end up with
the same Info being repeated in some of the fields.
I though that if I broke the table down into:
OrgNbr OrgNbr SubOrg1 SubOrg2
OrgName SubOrg1 SubOrg2 SubOrg3...
I would at least alleviate some of the redundancy. Now my
question - for anyone who has managed to follow thus far
is this. I have to associate a client with an Org, but do
I really have to store all of the Org and SubOrg numbers
with the client or is their another way? Right now we
have each client associated with an Org, but we want to
break down the Org into these separate pieces and then
associate the client with that. Can I get away with
storing just one number or do I have to associate all
SubOrgs and the Org with the Client?
Any ideas are appreciated.
C
I have to design a table or tables to contain the
following type of info:
OrgNbr
OrgName
SubOrg1
SubOrg2
SubOrg3
SubOrg4
SubOrg5
Each Org can have multiple SubOrgs so I would end up with
the same Info being repeated in some of the fields.
I though that if I broke the table down into:
OrgNbr OrgNbr SubOrg1 SubOrg2
OrgName SubOrg1 SubOrg2 SubOrg3...
I would at least alleviate some of the redundancy. Now my
question - for anyone who has managed to follow thus far
is this. I have to associate a client with an Org, but do
I really have to store all of the Org and SubOrg numbers
with the client or is their another way? Right now we
have each client associated with an Org, but we want to
break down the Org into these separate pieces and then
associate the client with that. Can I get away with
storing just one number or do I have to associate all
SubOrgs and the Org with the Client?
Any ideas are appreciated.
C