To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104023
User fs changed the following:
What |Old value |New value
================================================================================
Assigned to|dbaneedsconfirm |fs
--------------------------------------------------------------------------------
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
--------------------------------------------------------------------------------
OS/Version|Linux |All
--------------------------------------------------------------------------------
Priority|P3 |P4
--------------------------------------------------------------------------------
Platform|PC |All
--------------------------------------------------------------------------------
Summary|Field Properties in Form D|Cannot re/set "Input requi
|esign |red" property when "Empty
| |string is Null" is "No"
--------------------------------------------------------------------------------
Target milestone|--- |OOo Later
--------------------------------------------------------------------------------
------- Additional comments from f...@openoffice.org Wed Aug 12 13:19:06 +0000
2009 -------
Indeed, the *runtime* checks for the value of the InputRequired property, and
ignores the "Empty is NULL" property. Speaking strictly, this is correct: "Empty
is Null" is evaluated at the time a modification you do to the control is
committed to the database row (which is usually the case when you un-focus this
control).
The runtime check, however, is made *after* that, it it checks the database row
(before it is actually sent to the database) for fields which are NULL though
required. For any such field, if there is a control bound to it, which does have
"Input Required" set to "Yes", the runtime complains.
(In particular, if you travel to a new record, then the "Empty is Null" property
is *never* evaluated, as there's no user input to transfer to the database row.)
Design-wise, the "bug" is that "Input Required" is a per-control property,
instead of a per-database-field property. In the latter case, you could tell OOo
that for any control ever bound to that field, input is not required - once and
for all (instead of once for every control).
However, adding such client-side per-field properties is difficult for various
reasons, so it's a control property now.
The second bug is that "Empty is Null" has an influence on "Input Required"'s
enabled/disabled state. As explained above, both apply in different scenarios.
Perhaps the most feasible fix indeed is to simple remove that dependency in the
property browser.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
