[AccessD] Cannot Enforce Referential Integrity

Thanks John and Stuart.  She indicated that the joined fields were PK in 
parent table and FK in child table - but, I will double check.  Thanks 
for the thoughts.
Tina

John W. Colby wrote:

>Actually if the field in the parent is not designated the PK and / or no
>index on the child FK.
>
>John W. Colby
>www.ColbyConsulting.com
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart
>McLachlan
>Sent: Saturday, February 28, 2004 6:14 PM
>To: Access Developers discussion and problemsolving
>Subject: Re: [AccessD] Cannot Enforce Referential Integrity
>
>
>On 28 Feb 2004 at 15:28, Tina Norris Fields wrote:
>
>  
>
>>A student of mine is trying to remodel a database for her employer.  I
>>think the database was converted from A97 to AXP (A2K format).  She was
>>reviewing the relationships and wanted to enforce referential integrity
>>on one or more relationships.  She reports that the checkbox for
>>enforcing referential integrity was dimmed and unavailable.  I don't
>>know much more about this particular database.  Any ideas as to why the
>>enforce referential integrity choice would be made unavailable?
>>Thanks,
>>Tina
>>
>>    
>>
>Usually this happens if there is no unique index on the joined fields
>in the parent table.
>
>
>--
>Lexacorp Ltd
>http://www.lexacorp.com.pg
>Information Technology Consultancy, Software Development,System
>Support.
>
>
>
>--
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>
>
>  
>