VB Migration Partner’s support library hides most of the differences between the VB6 and the .NET versions of the DTPicker control, but not all of them. In most cases the remaining differences should have no impact on migrated programs. Here’s their complete list:

1. The Value property isn’t migrated to VB.NET. In most cases this isn’t a problem, because your code usually re-assigns it when a form loads, for example setting it equal to today’s date or a value read from a database. If this isn’t the case, however, you should make the assignment right in the Form_Load event handler, for example by means of an InsertStatement statement:

       '##  InsertStatement Me.DTPicker1.Value = #1/1/2000#

2. The VB.NET DTPicker control doesn’t support custom fields, therefore it doesn’t support the Format, FormatSize, and CallbackKeyDown events. These events are marked as obsolete.
3. The DateChanged property is set to True when a new value is assigned to the Value property, as in VB6. However, in the converted VB.NET application the Value property is assigned behind the scenes more often than in VB6, therefore you might find that the DataChanged property becomes True under certain circumstances in VB.NET but not in the original VB6 application.
4. The Format property isn’t migrated. For more information, see the following KB article:
   [PRB] DTPicker controls display their content using the LongDate format.
5. There is a discrepancy in how the MinDate property is initialized. For more information, see the following KB article:
   [PRB] The DTPicker control doesn’t accept dates earlier than 1/1/1753.