🚀 go-pugleaf

In article <9f4tn4$fvb$1@news.inet.tele.dk>, Birthe Weidinger
<birthe@unibase.dk> writes
>Try to set the fields format to the format you want ex. dd-mm-yy (shown as
>31-05-01)
>
>Birthe.
>
>"Henning Lang" <hlang@myrealbox.com> skrev i en meddelelse
>news:e6pP6.1$rB3.244@news010.worldonline.dk...
>> In all my tables and forms I've defined my date fields with a input mask
>of
>> 00 in the year fields. This works out fine except in one situation. On the
>> pc's where the application is to be used, the regional settings are
>defined
>> as yyyy as the year and therefore the "output" on the forms get showns as
>> yyyy. The problem is that when a user edits one of the date fields and
>> changes the month field they will also have to change the 2001 year to 01
>to
>> make it obey the input mask. Is there any workaround to this problem.
>>
Yup. Use the right date format to start with. If it's too much work to
go back and use full year entry (yyyy) throughout then you'll have to go
round looking for all the "Short Date", or whatever, formats and change
them to dd/mm/yy.

Do you remember the Year 2000 saga? I know quite a few applications
where that sort of thing can still apply even using Access's date
windowing. 

I used to train developers and one of my favourite examples was to have
them enter my father's birthday and my son's birthday using dd/mm/yy and
then looking at them using dd/mm/yyyy. If you try it you'll find that my
son is about 50 years older than his granddad. (1/2/1922 and 7/1/1974)
-- 
Albert Marshall
Database Developer
Marshall Le Botmel Ltd
01242 222017