Thanks for the feedback - that's exactly what I was after.
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:42***********************@per-qv1-newsreader-01.iinet.net.au...
The self-join is fine. The cascading update would probably be okay
unless
you had a circular relationship, e.g. a horse that was incorrectly
entered
as its own sire/grandsire/...
See:
Self Joins: tables that look themselves up (Pedigrees example)
at:
http://allenbrowne.com.au/ser-06.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"MDS" <md*********@yahoo.co.uk> wrote in message
news:42**********@news.bluewin.ch...
All,
I would like to implement a recursive relationship in a table with
referential integrity enforced and cascade update turned on.
For example, a horse has a sire and dam. Both the sire and the dam
must be horses and, therefore, drawn from the same domain.
Is it possible to implement this recursive relationship in Access 97
having "Sire" and "Dam" attributes in the "Horse" table?
----
MDS