[AccessD] setting referential integrity on a 1-1 relation

Philippe:

I'll bet that there's a record on one side that has no matching record on
the other side.  

I'd set up a query with both table and the PK from both tables in the grid.
Then run the query once with a left join and see if there is a PK on one
side with a blank on the other.  Then reverse the join - right join - run it
again, and again look for a PK on one side and a blank on the other.

HTH

Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

On 4 Mar 2009 at 10:55, philippe pons wrote:

> Dear list,
> I have troubles setting referential integrity between two tables, tProject
> and tForsys
> 
> The first is tProject(proj_id, ...) that stores data on projects
> 
> The second is tForsys(proj_id, ...) that stores other data on projects
> 
> Both tables store data of the same entity: a project.
> 
> Proj_id is the pkey of both tables.
> 
> I settled a 1 to 1 relation between both tables, on the pkey fields, and
> need to activate referential integrity. But I get an error message saying
> that project has data not ok for the link.
> 
> I check with a query that all tForsys.proj_id values are in the
> tProject.proj_id set of values.
> 
> Obviously, not all the tProject.proj_id values are in the tForsys.proj_id
> set of values as tProject is the main table. All projects are registered
> within tProject, but not all project s have a correspondant record
> within  tForsys
> !
> 
> Do you have any trick on how to settle referential integrity in this case?
> 
> TIA,
> 
> Philippe
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com