To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
--- Additional comments from phone...@openoffice.org Sun Jan 10 18:56:04
+ 2010 ---
I think at least should be warned in the field description.
---
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
--- Additional comments from f...@openoffice.org Thu Jan 7 14:17:28 +
2010 ---
not "now", probably ... I think that we should address this in the future, by
di
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
--- Additional comments from atjen...@openoffice.org Thu Jan 7 13:42:02
+ 2010 ---
But this was the decided upon design, client side only.
Is it now open to c
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
User fs changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
User msc changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
--- Additional comments from r4z...@openoffice.org Wed Jan 6 08:49:25
+ 2010 ---
Created an attachment (id=67016)
bugdoc
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108100
Issue #|108100
Summary|Table edit window not save default values to script
Component|Database access
Version|OOo