Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. a child row has multiple parents [modified]

a child row has multiple parents [modified]

Scheduled Pinned Locked Moved Database
questionxmlhelp
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kjetil Svendsen
    wrote on last edited by
    #1

    Hi All I have 4 tables in a dataset: ACTIVITY ACTIVITY_PARTICIPANT related to ACTIVITY (nested) PERSON related to ACTIVITY_PARTICIPANT (nested) ROLE related to ACTIVITY_PARTICIPANT (nested) if one person i related several times to one activity, with different roles, I get the "a child row has multiple parents" error. I understand why I get the error :-) My question is: How could I produce this xml from my dataset. Is there a method, or do I have to write it myself ? I guess I have to start with ACTIVITY ACTIVITY_PARTICIPANT related to ACTIVITY (nested) PERSON related to ACTIVITY_PARTICIPANT (NOT nested) ROLE related to ACTIVITY_PARTICIPANT (NOT nested) Thans in advance Kjetil modified on Wednesday, June 11, 2008 8:55 AM

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups