Are you _sure_ it used to work? SQL statements in Access have always
required that the dates be in mm/dd/yyyy format, regardless of what the date
format is set to via your Regional Settings.
In any case, you're probably running into a problem with the fact that
you're using 2 digit dates. When you were using 99 or 00 as the year, there
was no ambiguity: those numbers could only be years. However, now that
you've got 13/01/01, there's more than one way to interpret it. January 1st,
2013 becomes a valid possiblity, and Access is likely choosing that.
Doug Steele, Microsoft Access MVP
Beer, Wine and Database Programming. What could be better?
Visit "Doug Steele's Beer and Programming Emporium"
> Can anyone answer this, our report generator uses code likwe
> "select * from table where job_date between #"+format(11/01/01,
> dd/mm/yy)+"# and #"+format(13/01/01,dd/mm/yy)+"# order by etc"
> This has worked fine for 2 years until 13/01/2001, then it stopped
> working until I changed the format to mm/dd/yyy.
> Can anyonec explain this
> Kevin C Martin
> Sent via Deja.com