If you are working in a Client Server model with SQL Server there can be a problem with the date and datetime type attributes: they are incorrectly seen and processed.

For example: A record is inserted in a transaction entering the date 05/10/99. When the same record is consulted in Update mode the date shown is different from the one entered, for example: 28/02/13.

The problem appears when retrieving a date or datetime value from the database. Said value is read as a string, and it is assumed it has a certain format (the standard ODBC format for dates and time). In SQL Server the Windows regional settings (Control Panel/Regional Settings) can modify this setting if the Data Source option "Use regional settings when outputting currency, numbers, dates and times" is marked. That option is unmarked by default. This change in format causes the problem mentioned before.

Conclusion: The mentioned configuration parameter should not be modified when working with SQL Server.