[AccessD] Date Format

> This is from a data entry point of view, right?  Because dates are stored as
> numbers, so the 1930 to 2029 issue is a moot point.  
> 
> You can tackle this in one of two ways, at least that I can think of right
> now.
> 
> The first way is to get your data entry folks to use 4 year data entry,
> especially for earlier dates.
> 
> The second way is to just programmatically check the user.  On the Before
> Update event, put the following:
> 
> dim tmpDate as date
> tmpDate=Me.PatDate
> if tmpDate>date() then
> 	tmpdate=dateserial(year(tmpdate)-100,month(tmpdate),day(tmpdate)
> 	me.PatDate=tmpDate
> end if
> 
> The only issue you may run into, is a leap year, but since your 'moving' the
> date by a century, that shouldn't be much of an issue.
> 

Au contraire :-)
This is the only time in 400 years that it IS an issue.
2000 is a leap year, 1900 is not.



-- 
Lexacorp Ltd
http://www.lexacorp.com.pg
Information Technology Consultancy, Software Development,System Support.