Please note that it is important to consider the value of this parameter in your connections and the corresponding settings of the QuickBooks. In many cases QuickBooks may display different values than set or returned via dotConnect for QuickBooks because of different time zone settings in your SqlShimConnection and in QuickBooks. For example, if you set UtcDates to true, and QuickBooks is configured to display datetime values in your local time, when you specify a datetime value in an INSERT or UPDATE statement, it is treated and sent to QuickBooks as a UTC value. When displaying this value in the QuickBooks interface, QuickBooks converts it to your local time, and thus displays a different value than the one that was specified in the INSERT or UPDATE statement.
The same is correct when selecting data. If UtcDates is set to true, and QuickBooks is configured to display datetime values in your local time, the date values returned via dotConnect for QuickBooks may differ from the values, displayed by QuickBooks. This happens because in this example QuickBooks convertsthe values to your local time when displaying them, and dotConnect for QuickBooks doesn't.
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2