Dynamic table structure-needed?

[CadMonkey]

You should have:

tblHeadings and tblHeadings_1

I do, that's no problem- it's just the link between the two I can't figure... I join the SectionID to the ParentID of the table and the Schedule ID to the Schedule ID (because the primary table is two part PK), enforce ref.integrity, and apparently I am missing records in the adult table---- But I'm not I swear!!!! SO am I linking the wrong fields I wander?

It's a crazy world in computers...

 

[CadMonkey]

In conclusion...?

Hey, just to let anyone know and see if the pooled knowledge is far superior to mine? Can anyone actually create a 1 to many relationship within one table?! I know the theory, tblheadings_1 etc but the fields with which to link just escape me.

 

[Len Boorman]

Not sure about this but

Is it possible to link tables when you have a multi field PK in the Parent Table. I Have doubts. Let me explain.

Yes I believe it can be done and is covered within Relational Database theory. I also believe that SQL within DDL covers the situation but doing it within the Relationship display of Access. Hmmmmmm I have my doubts


I think (but am not certain) that it may be necessary to create a single key PK to link with another field acting as the FK

JUst thoughts

Len B

 

[CadMonkey]

And your final answer is...

I see where your coming from. I think it can be done within the Access window though. Does anybody know a final conclusive answer or maybe even have an example for us to oggle at? An Access Compatible recursive relationship... one man's dream...

another mans nightmare!

 

[Mile-O]

I posted this one yesterday for somebody...

 

[CadMonkey]

Sorted.

Thankyou very much! This is an excellent simple illustraion of using the recursive functions

 

[CadMonkey]

Columbo again...

Just one more thing...

I think it is impossible to have a multipart key in a recursive table and have this same relationship??