Issue 37669 - date entry in table fields resetted if format wrong
Summary: date entry in table fields resetted if format wrong
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.3
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2004-11-23 07:14 UTC by vamshi11us
Modified: 2013-02-07 22:35 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description vamshi11us 2004-11-23 07:14:14 UTC
Created a dbf table .

tried inserting data in date field , when invalid dates are entered in correct 
date format with separators like 56/56/56 and saved , no error message is 
when i try to enter values in next record the invalid date is replaced with 
default date 12/30/99.
when same invalid date is given without separators like 565656 and saved still 
no error message is thrown .
but default date is replaced when i try to enter values in next field.
Comment 1 vamshi11us 2004-11-23 07:21:19 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 
Comment 2 marc.neumann 2004-11-23 07:39:31 UTC
correct prio to 3

see for details
Comment 3 flibby05 2005-04-24 15:26:34 UTC
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
Comment 4 alex.thurgood 2005-08-15 22:12:26 UTC
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.

Comment 5 Frank Schönheit 2007-07-03 09:10:15 UTC
Who is "developer"? Back into pool
Comment 6 christoph.lukasiak 2007-09-03 16:07:27 UTC
feature enhancement