Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Breaking and reestablishing relationships

Discussion in 'Information Technology' started by tcb, Nov 8, 2005.

  1. tcb

    tcb
    Expand Collapse
    Guest

    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
     
  2. Loading...

    Similar Threads Forum Date
    Sikh News BREAKING: Young Sikh Shot Dead In Jalalabad, Afghanistan . - Sikh24 News & Updates Breaking News Oct 2, 2016
    USA AP Breaking News: Sikhs Added to Hate Crime Stats Breaking News Aug 3, 2013
    Pacific Scandals breaking like China dolls Breaking News Jul 10, 2013
    1984 Bluestar: Breaking the Wheel of Dharma History of Sikhism Jun 4, 2013
    India BREAKING NEWS: Growth needs hard decisions: PM Breaking News Sep 22, 2012

  3. MacDermott

    MacDermott
    Expand Collapse
    Guest

    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.


    "tcb" <tbenson@mn.rr.com> wrote in message
    news:1131366586.049105.236770@f14g2000cwb.googlegroups.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
    >
     
  4. tcb

    tcb
    Expand Collapse
    Guest

    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).

    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?
     
  5. MacDermott

    MacDermott
    Expand Collapse
    Guest

    I don't see a problem -
    Import your tables in this order:
    tblAgency
    tblCourse
    tblCourseDetail

    "tcb" <tbenson@mn.rr.com> wrote in message
    news:1131372079.761641.228700@g44g2000cwa.googlegroups.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).
    >
    > 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?
    >
     
  6. tcb

    tcb
    Expand Collapse
    Guest

    I'm no good at chess either.

    Initially I was getting "records not imported" type errors which had I
    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.
     

Share This Page