Microsoft KB Archive/155546

= TMGR: Changing Field Default Changes Unmodified Entries =

Article ID: 155546

Article Last Modified on 8/17/2005

-

APPLIES TO


 * Microsoft Team Manager 1.0 Standard Edition

-



This article was previously published under Q155546



SYMPTOMS
In Team Manager, when you change the default value of a custom field, the value of that field changes to the new default value for any row in which you have never specifically selected or entered a value.



MORE INFORMATION
Team Manager enables you to create and insert various types of custom fields into tables. You can specify a default value for all of the types, except for the OLE Object type. For many of the custom field types, such as custom Currency and Duration fields, you can specify a restricted list of choices for the field. Custom fields with a restricted list display a drop- down button in the field when selected. Custom Date Range and Date/Time fields also display a drop-down button when selected, enabling you to select a date range or date from a calendar.

If you never manually entered or selected the value in a custom field in a non-empty row from a drop-down list or calendar, then changing the default value for the custom field causes the corresponding value in that row to change to the new default value.

The following example illustrates this behavior.

A custom number field called "Number Field 1" with default value 1 and a restricted list of 1, 2, and 3 was inserted into a task table, and the current values of three tasks are shown below:   Task Name        Number Field 1 -       --   TaskA            1 TaskB           1 TaskC           2 TaskA was never modified. For TaskB, 1 was selected from the drop-down list in the custom number field (even though the cell already displayed a 1 by default). For TaskC, 2 was selected from the drop-down list.

The default value for the number field was then changed to 3, resulting in the following values:     Task Name        Number Field 1 -       --     TaskA            3 TaskB           1 TaskC           2 NOTE: The value in the custom number field in TaskB did not change to 3 because the 1 had been specifically selected from the list.

