Greg,

   The original table definition has a contrain declaration that do not include contrct_number as part of the key, in that case if the user creates two itemsources with the same start & end dates but different contract number for the same item, it shows an error. For example imagin you receive a contract for 200 pieces and you sell them all, you call the vendor and request another 100 and the vendor gives you a new contract number, still the same item, the same time period but different contract. The actual constrain prevent that so I added the contrct_number field to the constrain to fix that. The change should be this:

      REFERENCES vendinfo (vend_id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE CASCADE,
  CONSTRAINT itemsrc_itemsrc_vend_id_key UNIQUE (itemsrc_vend_id , itemsrc_item_id , itemsrc_effective , itemsrc_expires , itemsrc_vend_item_number , itemsrc_manuf_name , itemsrc_manuf_item_number , itemsrc_contrct_id )

instead of 

      REFERENCES vendinfo (vend_id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE CASCADE,
  CONSTRAINT itemsrc_itemsrc_vend_id_key UNIQUE (itemsrc_vend_id , itemsrc_item_id , itemsrc_effective , itemsrc_expires , itemsrc_vend_item_number , itemsrc_manuf_name , itemsrc_manuf_item_number )

I don't know why is not marked as changed but if you check the original database of 4.2.0RC itemsrc constrain it do not include the contrct_number.

Regards