Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | date entry in table fields resetted if format wrong | ||
---|---|---|---|
Product: | Base | Reporter: | vamshi11us <vamshidharm> |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | flibby05, issues |
Version: | OOo 1.1.3 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
vamshi11us
2004-11-23 07:14:14 UTC
and when the query is run , after entering the invalid date fields , still it is displaying invalid dates . like select * from table_name; the invalid dates entry is given in attachment correct prio to 3 see http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority for details hi vamshi11us,
>>the invalid dates entry is given in attachment
please attach the sample file, thanks.
ps: from having a quick look at the dbf format i think that it supports text
fields, only? This would then explain, that OOo at the same time seems to
correct incorrect date fields when enterning them in OOo, but will save them in
non-date-format.
Hi all, This is also the behaviour with the 1.1.x branch. I can also confirm that this is the case with date fields connected via ODBC to a mysql server. If an invalid date entry is made, no matter whether through a form or directly in a table, the invalid date is not checked, even if the option in the Control Properties is set. What OOo does however, is make the user believe that the entry is correct, and then switch it back to the OOo default start date of 1899. Confirming the behaviour. Alex Who is "developer"? Back into pool feature enhancement |