Le 24/06/11 21:37, Tom Cloyd a écrit : Hi Tom,
> Thanks for this thorough investigation of the behavior I described. I'm > glad it was replicated. I don't think this problem is (for me anyway) > much of an impediment, but I HAVE noticed other problems with default > values. To wit: default values set up in the table designer, do not > appear in forms when a new record is created and the table field is > linked to list box. The list box display remains blank. This happens if > the default value is in the table, OR if it's set in the list box > properties. Neither has any effect in the form, not even when the > table/view browser (press F4 to get this) is active. Known behaviour, and this is actually currently by design (well it was designed by the people at Oracle). The table/field creation functionality does not transmit default values to the underlying database, you are supposed to use a corresponding form for this and define the default there rather than at the database level. This was done because it was felt it was too difficult (i.e. developer time intensive) for OOo to be able to manage all of the possible driver return handling for all of the various possible database connections out there. However, it does appear that even the form based default setting of values does not work as intended, i.e. the values are not necessarily passed from the form to the underlying db...File a bug, if you like, but I'm pretty sure one has been filed already. Alex -- Unsubscribe instructions: E-mail to [email protected] In case of problems unsubscribing, write to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
