Reverse Parent/Child

[Leif]

I have a task to create tracking of projects and subprojects. Its sounds
like a simple 1 to many relationship with the parents FK in the child table.

However, in this case the subprojects are created first, then later rolled
up to a project. So, I've not been able to get the typical form/subform
parent/child arrangement to work. When a "add" a parent record (project) the
system wants to add a child record (subproject), but the subproject already
exists.

I can probably do it with coding. I also can probably do it with an
intersect table that I would normally set up for a many to many relationship.

Has anyone had the situtation and solved it without a third table or a bunch
of coding?

Regards,
Leif

 

[Jeanette Cunningham]

Hi Leif,
I haven't had a need to do this. However one way could be to establish the
parent table in the database right from the start.
Let each sub project have its own parent record in the parent table.

When you want to transfer a group of sub projects to the same parent, you
could use an update query to change the parent ID for those sub projects so
that they all have the same parent.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Leif]

Hi Jeanette,

When you say "establish the parent table in the database right from the
start" do you mean establish the parent table record? If each sub-project
(child record) has a project record (parent record) then is that not 1:1
instead of 1:M? And then I guess I would need to hide all these parent
records? Perhaps I'm not understanding your suggestion?

Regards,
Leif

 

[KARL DEWEY]

Have one-to-many but use a Temp parent record title something like 'Planning'.
Then when you create the Real project record just update the sub-project
records from Temp to Real.