On Monday 27 July 2009 11:30:36 am Miguel Lopes wrote: > The general solution is setting a default value in the bizobj (that is > of course in the Keys list of the dropdownList).
I believe that will not work (unless the default value is set to zero (0)). I think you are not understanding what is the root cause of the error. In the DB you have a field that is associated with the dropdown. There is a record with the field that contains a value that is not in the 'Choices' or 'Keys' of the dropdown (depends on ValueMode). The value in the field could be a Null. In fact I think you have suggested that the value is a null. In Dabo Nulls are converted to '<None>' (in most cases) for strings and zero for numbers (not sure if numbers are converted - Hmmm). So if your keys for the dropdown contain numbers (1,2,3,4) and the field contains a null (or 0) you will get the traceback. So adding the values '<None>', and zero to the Choices, Keys causes the error to go away. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
