Yes I do see a problem.  You can force the person to enter 10/07/2007, but is that Oct 7 or July 10?  Although Canada has a standard date format, few actually adhere to it.  I've seen a good deal of mix in Regional Settings - some are set to dd/mm/yyyy and just as many to mm/dd/yyyy.

So their entry of 10/07/2007 will be interpreted by Access according to the Regional Settings on the computer.  The user might not be aware of their settings and intend something different.  To further muck things up, Access will spin a date around if it doesn't conform to the Regional Settings until it does get a valid date - i.e. Regional Settings set to mm/dd/yyyy and the user enters 14/07/2007.  That's not a possible date for the RS, so Access spins it to 07/14/2007 or possibly 07/07/2014.  Then you'll get users claiming that 'sometimes' Access gets the date wrong.

An input mask on a date field just slows people down.  You can enter 10/7 (or 7/10 if that's your RS) and Access will assume the current year.  If you force the input mask, you're asking them to enter 6 more keystrokes unnecessarily.  In addition, the input mask demands that they enter your 10 keystrokes.  Without the mask the user has the freedom to enter the date any way they wish...
Jul 7
July 7, 2007
7/7
7/7/7
7/7/2007
will all be accepted.  Even those who don't know the shortcuts in Access can still enter the date any way they wish.  Over time you can train users on the quick entry methods.

What you need to be concerned with is the fact that users may not know what their RS is set to; you want to be certain that Access interprets their entry correctly.  Set the format of the control to an unambiguous date format such as dd/mmm/yyyy or mmm/dd/yyyy.  That way the user will see right away whether the date was taken as they intended.