Hi there

Would anyone have any idea why Access 2000 accepts 31st September as a valid
date even when entrered into a date/time fiield in a database. It's occured
one more than one database so it doesn't appear to be down to the design of
the database.

If you could help i'd be very grateful.

Many thanks

David.

I can't get it to do that in several different versions. Perhaps you have
the datatype set to Text.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"David Gartrell" <(E-Mail Removed)> wrote in message
news:vp6dnVYhDe-(E-Mail Removed)...
> Hi there
>
> Would anyone have any idea why Access 2000 accepts 31st September as a
> valid date even when entrered into a date/time fiield in a database. It's
> occured one more than one database so it doesn't appear to be down to the
> design of the database.
>
> If you could help i'd be very grateful.
>
> Many thanks
>
> David.
>
>

Access MDB isn't reliable enough for enforcing simple datatypes.

I would reccomend using Access Data Projects and just spit on anyone
that still uses MDB.

MDB isn't even supported in the next version of Office.

-Aaron




Arvin Meyer [MVP] wrote:
> I can't get it to do that in several different versions. Perhaps you have
> the datatype set to Text.
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
> "David Gartrell" <(E-Mail Removed)> wrote in message
> news:vp6dnVYhDe-(E-Mail Removed)...
> > Hi there
> >
> > Would anyone have any idea why Access 2000 accepts 31st September as a
> > valid date even when entrered into a date/time fiield in a database. It's
> > occured one more than one database so it doesn't appear to be down to the
> > design of the database.
> >
> > If you could help i'd be very grateful.
> >
> > Many thanks
> >
> > David.
> >
> >