Ever since Access 2.0, i have been using fields of type long integer
as a subsitute for date fields, since I don't need the time part most
of the time. Setting the fields format property (or the format
property of a bound textbox) to "short date" not only showed the
stored number as a date, it was also used as an input mask: you could
only enter values that corresponded to valid dates as indicated by the
local windows settings. This was comparable to formatting Excel cells
as "date".
In Access 2007, this sup****t is halfway gone. It still works for
unbound text boxes (even displaying the date picker), but with text
boxes bound to a database field of type number or in a table view,
only the display part is correct. Data newly inputted is interpreted
as a plain number. Since the german date delimiter is the same as the
thousands separator, it took some time to figure out what is really
happening. For example, a date entered as "29.07.08" is interpreted as
ISO Date 2008-07-29 in Access 97-2003, but as the number 290708 in
Access 2007, which is then converted to ISO date 2695-05-12.
I could not find this change in behaviour do***ented anywhere. Am I
the only one experiencing this problem, does anybody know a solution
to this problem? Can it be solved at the form level? I really don't
want to change the type of hundreds of database fields, since this
would lead to a massive size increase and also pose integrity problems
as I wold have to make sure the time part is always "zeroed out"
before saving.
Thanks in advance
Reimund
|
