This article has been archived. It is offered "as is" and will no longer be updated.
When you make changes to enterprise custom fields in your Master Project File in Microsoft Office Project 2003, enterprise custom field values that are contained in a task may be missing from the inserted file, and other task data may randomly disappear.
Additionally, when you save a file, you may receive a SQL error message that is similar to the following:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert duplicate key row in object 'MSP_TASK_BASELINES'with unique index 'I_MSP_TASK_BASELINES'
In some cases, the SQL error message that you receive may have "MSP_ASSIGNMENT_BASELINES" instead of "MSP_TASK_BASELINES," and the corresponding index is "I_MSP_ASSIGNMENT_BASELINES"instead of being "I_MSP_TASK_BASELINES."
This problem may occur if all the following conditions are true:
You save your project plan to your Microsoft Project Server, or you save your project plan as a Master Project File (*.mpp).
You make changes to Enterprise Custom Fields.
You add new tasks with Enterprise Custom Field data to your Master Project Plan.
You save the changes to your project plan, and then restart Microsoft Office Project Professional 2003.
You add Enterprise Custom Field data to tasks that you entered earlier that did not previously contain Enterprise Custom Field data.
You have more than one Enterprise Custom Field that is defined for any particular entity (task, resource, or assignment) in the project.
Service pack information
This problem is corrected in Project 2003 Service Pack 1.
To resolve this problem, obtain the latest service pack for Project 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
873459 How to obtain the latest service pack for Project 2003
How to obtain the hotfix
This issue is fixed in the Microsoft Project 2003 Hotfix Package that is dated April 21, 2004. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
840659 Microsoft Office Project 2003 hotfix package: April 21, 2004
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Project 2003 Service Pack 1.