Breaking and reestablishing relationships

Is the relationship between two tables an object that can be
maniuplated in code? Setting referential integrity, relationship type,
cascading deletes and such?

I'd like to break the relationship to several tables, import records,
then reset the relationships (one to many).
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/6844-breaking-and-reestablishing-relationships.html
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844

tblCourse --> tblCourseDetail

tblCourse <-- tblAgency


*

 
Do share your immediate thoughts or reactions on this issue? We value your views! Login Now! or Sign Up Today! to share your views with us.. Gurfateh!

While this can be done, it's rarely a wise approach.
Usually it's enough to import into the "master" table first, then the child
table.
If there are items in the data to be imported, which you don't want to keep
because they break referential integrity, I'd suggest importing to a
temporary table and using a query to identify those items.


Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844
"tcb" wrote in message
news:1131366586.049105.236770@f14g2000cwb.googlegr oups.com...
> Is the relationship between two tables an object that can be
> maniuplated in code? Setting referential integrity, relationship type,
> cascading deletes and such?
>
> I'd like to break the relationship to several tables, import records,
> then reset the relationships (one to many).
>
> tblCourse --> tblCourseDetail
>
> tblCourse <-- tblAgency
>

The way the database was set up, there is a one-many relationship
between tblCourse (master) and tblCourseDetail (child).

There is a one to many from tblAgency (master) to tblCourse (child).
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844

In one case tblCourse is the master and in the other, the child, which
creates the dilemma.

How is the relationship object referred to in VB?

I don't see a problem -
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844
Import your tables in this order:
tblAgency
tblCourse
tblCourseDetail

"tcb" wrote in message
news:1131372079.761641.228700@g44g2000cwa.googlegr oups.com...
> The way the database was set up, there is a one-many relationship
> between tblCourse (master) and tblCourseDetail (child).
>
> There is a one to many from tblAgency (master) to tblCourse (child).
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844
>
> In one case tblCourse is the master and in the other, the child, which
> creates the dilemma.
>
> How is the relationship object referred to in VB?
>

I'm no good at chess either.

Initially I was getting "records not imported" type errors which had I
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=6844
looked closer were not key violations. The developer had added
validation rules to the new tables.

Nonetheless I still missed what will be forever obvious now.

Thanks.