I have an application that consists of an Access 2010 FE with a SQL Server 2012 BE. This application has been evolving over approximately 20 years, and has seen many different programmers, I am simply the current programmer.
The way that the program has been coded, requires users to have their short date format set to month/day/year, which Windows has declared to be US format (I am in Canada). We also have the SQL Server login set to MDY. We have a client that is experiencing a problem with the dates in the program, that we believe is caused by the following combination:
The date format on the server that is hosting the SQL Server is set to mm/dd/yy. A 2 digit year.
The server interprets 2 digit years a being between 1900 and 1999.
This is causing formatting problems with some of the date fields throughout the program. The program is using a four digit year in some places and a two digit year in others. In some instances of the two digit year, it has the year correct as 2013, and in other locations, it interprets the two digit year as 1913.
I am wondering if there is a way to overcome this problem. In the locations that the program is misinterpreting the date, I have tried to explicitly format to a four digit year, and that is not solving the problem.