1 Reply Latest reply on Mar 1, 2010 8:50 AM by jonnyt

    Forced one to one relationship

    jonnyt

      Title

      Forced one to one relationship

      Post

      I have a script that imports some data from an xml feed from the internet. The data imports into a related table defined by Foriegn Key: ourReference

       

      We then have a calculation field that summrises soem data from the main table and also displays the related data from the related table.

       

      We then need to paste this information into an external web system. This is where the problem occurs.

       

      If there is no related data in the second table the calculation seems to pick up data from another record.

       

      how can I stop this from happening?

       

      The calculation is shown below and the related data is from the hpi_data table e.g. hpi_data::Model

       

      When no related data is present in the hpi_data table, the calculation seems to pick up data from another record. HOW CAN I STOIP THIS FROM HAPPENING?

       

       

      "---------- Database data----------" &  ¶  &
      "Our Reference: "  & Our Reference & ¶ &
      "Their Reference: "  & Their Reference  & ¶ &
      "Reg: "  & Upper ( Reg Number)  & ¶ &
      "Vehicle: "  & Upper ( Vehicle)  & ¶ &
      "Engineers ID: " & Engineer ID  & ¶ &

      "RELATED DATA" & ¶ &
      "---------" & ¶ &
      "MAKE: " & hpi_data::Make & "    |     MODEL: " & hpi_data::Model & ¶ &
      "YEAR OF MANUFACTURE: " & hpi_data::Mfr_Year & ¶ &
      "ENGINE SIZE: " & hpi_data::Engine_Size & ¶ &
      "YEAR OF REGISTRATION: " & hpi_data::Date & ¶ &
      "VIN/CHASSIS: " & hpi_data::Vin & ¶ &
      "-----------------------------------------------------"