Hi Eugenio,
Thank you for that pointer.
I have found the culprit, it was as you suggested a duplicate value in a lookup field. Two rows in the linked table had the value zero and when I reset the rogue duplicate to NULL, my problem went away.
So, not a DaDaBIK issue at all - it was a data...