Re: PK & FK problems in data consolidation
- From: Frank Situmorang <hfsitumo2001@xxxxxxxxx>
- Date: Thu, 30 Oct 2008 23:28:01 -0700
Thanks Michael, yes I understand a bit aobut your jargon...he...he..he.I am
not an English speaker...so maybe that is one reason that I run in the circle.
I agree with you that it should be using a multi field primary key, but
what bothers me I think it is difficult to operate.
Rignt now I have an input form of a member and in this form I have a combo
box to choose his address. With this 4 field PK of address, how can I make it.
When I input the member ID with the 4 field PK, how can I do it. Isn't it
too complicated for a church secretary to operate?
Thanks for your advice
H. Frank Situmorang
"Michael Gramelspacher" wrote:
On Thu, 30 Oct 2008 00:30:05 -0700, Frank Situmorang <hfsitumo2001@xxxxxxxxx> wrote:.
Tom...my problem is quite complex chruchID within the region yess. it is not
duplicate, but as I said in my other postings, that our organization is is a
multilevel,
The highest is GC ( General Conference) which is a world office which is
consist of 13 Division, then Division consists of Union and Union consits of
Region. Like us in Indonesia is part of West Indonesia Union, and Union
consits of Region, the Region consists of Churchses
Yes your suggestion could be right if the churches for the region, but if
the church is in another region, of course their churchid sould start also
from No.1
The same is true fo the RegionID, if it is in the other Union, the RegionID
should start also from no.1, so there will be a duplicate regionID from other
Union (upper level). The same is true also for the UnionID, will duplicate
with the other UnionID from other DiVisions, This is not the case with the
Division because only one office for the world level, and I have got its
Acronym and can be used as it's ID
I do knot know if Access database can handle this kind of hirarchy, each
herachy will consolidate the data from it's lower offices.
Thanks for any idea
You are running around in a circle like a dog chasing its tail and getting nowhere.
Members table and Addresses table at all levels can have the same structure. The key will be
MemberID, ChurchID, RegionID, UnionID, DivisionID, that is, a multi-column primary key. Everyone is
happy. Everyone's member table structure is the same as everyone else's. Same goes for addresses.
I assume each church is not making up their own RegionID, UnionID and DivisionID numbers. Do
regions make up numbers for their churches? Do unions make up the numbers for their regions, etc.?
- Follow-Ups:
- Re: PK & FK problems in data consolidation
- From: Michael Gramelspacher
- Re: PK & FK problems in data consolidation
- References:
- PK & FK problems in data consolidation
- From: Frank Situmorang
- Re: PK & FK problems in data consolidation
- From: Tom van Stiphout
- Re: PK & FK problems in data consolidation
- From: Frank Situmorang
- Re: PK & FK problems in data consolidation
- From: Michael Gramelspacher
- PK & FK problems in data consolidation
- Prev by Date: Re: Main form with subform
- Next by Date: Re: Main form with subform
- Previous by thread: Re: PK & FK problems in data consolidation
- Next by thread: Re: PK & FK problems in data consolidation
- Index(es):
Relevant Pages
|