A family of Microsoft relational database management systems designed for ease of use.
i will add on to John's answer that Acccess goes to great lengths to interpret a wide variety of dates that might be entered by users, and I find that very convenient, both as a user and as a developer.
It would be possible to use an input mask to restrict the sorts of date entries that users can make, but it still wouldn't help you in keeping a user from entering "13/12/2012". And you could use code in the text box's BeforeUpdate event to examine the actual text the user entered and possibly reject and entry such as "13/12/2012", but:
- That won't help you determine whether an entry "7/9/12" means July 9th or September 7th, and
- If the user enters "13/12/2012", don't you really know what they intended, anyway? Why not just let Access correct it?