I am not quite sure of the problem, but I have had similar experiences. Things depend partly on what is in your Windows Settings/Control Panel/Regional Options/Date: by default Access uses the format you have set there. I develop using ISO dates(yyyy.mm.dd) on my PC, as this is natural to the Gregorian calendar. Most of my users have their PCs set to half-backwards numeric(mm/dd/yyyy or mm/dd/yy), more or less natural to the English variant of the Julian calendar. The databases I give them workon their PCs. In the criterion(yes, I know that some fool officially made it plural), I put the date from the screen inside the function DateValue for comparison. Here is an example from my code:
stLinkCriteria = "[BISNumber]=" & Me.BISNumber _ & "and [SessionDate]= DateValue('" & Me![SessionDate] & "')"
If DCount("[BISNumber]", stDocName, stLinkCriteria) = 0 _
Then
DoCmd.OpenForm stDocName, , , , , , Me.BISNumber & ":" & Me.SessionDate Else
DoCmd.OpenForm stDocName, , , stLinkCriteria
End If
I have also successfully put ISO-format date constants in my VB code, but I do not think it would work to put ascending-format constants in and then run with the Windows setting half-backwards.