On Jul 27, 2009, at 6:25 PM, Miguel Lopes wrote:
>> 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.
>
> Not exactly. All column values for existing records are within the
> 'Keys' list of the dropdown.
> Only when a new record is created (which in the DB defaults to Null),
> the bizobj converts it to 0 (zero).
> Hence, when the dropdown fetches the value from the bizobj, we have an
> exception, which is pretty much what I figured as well.
>
> So for praticallity, when there is a restriction on the value (like
> the case of a 'Choices' or 'Keys'), and if the default value assigned
> by Dabo's bizobj is different, one *must* assign a default value on
> the bizobj.
The fundamental problem here is that when creating a new, blank
record, Dabo doesn't know if a column is nullable or not; it creates
'blank' values, which, in the case of columns of type integer, results
in 0 values.
In this case, then your observation that you must tell the bizobj
what to do when creating a new, blank value is correct. It can only
guess so much.
-- Ed Leafe
_______________________________________________
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]
