Problem with UK style Short date style (dd/mm/yyyy) - it's REALLY wierd!

[Sharky II]

Hi guys, while helping me with some stuff on my DB, hayley pointed out wierd quirky thing in access with regards to the UK date format

Originally she told me i was using US format - but in the table it had the date format in dd/mm/yyyy

however the # symbol in the coding is representing US dates ie try searching for 12/06/03, guaranteed it is more likely to read this as 6/12/03.

She suggested that i remove the #'s but then i got nothing... she explained

"Regarding the US fromat - I noticed when takin gout the # symbol it didn't return dates because VB reads it as 12/06/3 instead of 12/06/03 in otherwords it misses out the 0 therefore doensn't display the records it should. Must be something else required in the coding. The only way I've got round this is to use Medium date - see the example I sent you! "

Many thanks to hayley for that. I couldn't imagine that sneeking up on me, because the only dates which have a problem are ones which have the first two numbers of the date (xx/mm/yyyy/) which are smaller than 13!!!!

So does anyone know how to fix this, without using medium date format? It's not a big deal to use medium date format but a) i'll have to change things and b) it's pretty wierd stuff!!!

Cheers - ask for any more info if needed!!

Edd

 

[Rich]

The problem comes when using/returning dates in strings.
Use the Format function to overcome the problem

 

[Jon K]

Take a look at Pat's post in this thread:

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=54145&highlight=date

 

[Hayley Baxter]

Thanks for that link Jon. I battled with that problem for a while and in the end just found a work around for it. At least now I can go back and correct the problem.

Thanks very much
Hay