I had a great support call today. I have this Access database at work which is my responsibility to keep functioning. So when problems occur I have to backtrack through data and code for hours on end trying to find out what went wrong. What makes this really frustrating is the guy who wrote this (a professional contractor) didn't label any of the text boxes on any of the forms or in his code. So every time I look at code it all says stuff like "x = Text25". This is a complete nightmare to work with and makes the task of fixing the database more complicated than it needs to be.
Anyway, this guy came in saying that it was messing up the dates, which is a new problem as far as the database was concerned. Every time he entered the date 31/06/06 it said that it was 06/06/1931. So I said leave it with me and I set about stating to do what he was doing. Those of you who are observant will have noticed this already. He was entering a date that didn't exist, and it took me about 3 minutes of entering dates into the system to notice this. There are only 30 days in June so Access was doing it's best to convert the string into a date. I went over to his office and said "How many days are there in June?", so which he said "...oh...". Ah, the life of a database adminstrator.