[AccessD] Relationship Issue

..ok ...maybe my thinking cap isn't on straight ...but I don't see how what 
you describe can work ...from what you say you only have two tables and yet 
you want to enforce referential integrity AND do cascade deletes ...setting 
aside for the moment my long held animus for cascade deletes, I don't see 
how you can have referential integrity in the first place, eh?

..in my little world I need a tblEmployees, a tblJobs, and a tblEmpJobs 
that holds the FK for each job assigned and the FK for each employee it was 
assigned to ...else I wind up with duplicate Jobs in the tblJobs and/or dupe 
employees in tblEmployees ...assuming jobs are not unique to employees of 
course but if so, then why separate tables at all.

..but like I said, its been a mind bending day and maybe I'm not quite 
seeing the light as well as I should ...if so, I'm sure someone here will 
point out the error of my ways.

William Hindman


----- Original Message ----- 
From: "Joe Hecht" <jmhla at earthlink.net>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Tuesday, December 28, 2004 8:28 PM
Subject: [AccessD] Relationship Issue


>I have a table  Employees and a subtable stblEmpJobs.
>
> They link on field EmpID
>
> The link was built when I built and dropped the forms together. The
> relationship in the window says one to many ( external ). I need to edit 
> the
> relationship to enforce referential to do permit cascade deletes.
>
> Any ideas ?
>
> The customer has signed off they do not want to archive ex employees in 
> the
> system. She wants to  pull the paper records
>
>
>
> JOE HECHT
> LOS ANGELES CA
> jmhla at earthlink.net
>
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>