philippe pons
phpons at gmail.com
Wed Mar 4 04:56:30 CST 2009
Gustav, thanks for your answer Stuart,you hit the point and saved my life! It's exactly what I did wrong. Thank you! Philippe 2009/3/4 Stuart McLachlan <stuart at lexacorp.com.pg> > tProject must be the Left hand table in the relationship window. > tForsys is the "Related Table" > > When creating the relationship make sure you drag from tProject to tForsys > not the other > way around. > > -- > Stuart > > > 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 >