Microsoft KB Archive/142800

= PRJ: Microsoft Project and Microsoft Access Database Replication =

Article ID: 142800

Article Last Modified on 10/7/2003

-

APPLIES TO


 * Microsoft Project 4.1 Standard Edition
 * Microsoft Access 95 Standard Edition

-



This article was previously published under Q142800



SYMPTOMS
In Microsoft Project, when you save information to a Microsoft Access database using ODBC, you may receive the following error message in Microsoft Access:

Duplicate value in index, primary key, or relationship. Changes were unsuccessful.

The information about the specific project file in the Design Master and Replica databases will not change.



CAUSE
The Microsoft Project Save To Database feature does not take replication scenarios into account. If the Microsoft Access database is replicated, errors will result during the synchronization if a specific project file is modified in two different databases in the replica is set prior to synchronization.



WORKAROUND
To work around this problem, use the following rules:


 * 1) The first time the Microsoft Project Save To Database feature is used to store information in a Microsoft Access database, four tables will be created by the Microsoft Project Save to Database menu item. This process must be done on the Design Master of the replica set. Only the Design Master can make changes to the structure of the database.
 * 2) If the Microsoft Project Save To Database feature is used to store information in a Microsoft Access database that is already replicated and did not have the Microsoft Project Table structure before being replicated, the new Tables created by Microsoft Project will need to have the "Replicated" property set manually in Microsoft Access.
 * 3) New project information should only be saved to one database in the replica set between synchronization. This information will then be successfully replicated between the other databases in the set during synchronization.
 * 4) Data in the Microsoft Project-defined tables in the databases should not be modified directly in Microsoft Access. Modifying the project data in Microsoft Access is not supported and can cause errors when you import the data back into Microsoft Project. Additionally, if data were to be modified in two databases before synchronization occurs, you will receive the error message described in the "Symptoms" section of this article.
 * 5) By default, Microsoft Project will not be able to save a single project file to two different databases in the replica set. Microsoft Project retains information regarding the database that the project file was saved to in the project .mpp file.

To allow a project file to be saved to a database in the replica set other than the original database, a text string in the .mpp file must be modified to direct the Save To Database to the new location.

NOTE: This procedure is only relevant for a project that has already been saved and replicated to the replica set. New projects can be added to any database in the replica set at any time, as long as they are not added to two different databases in the replica set before synchronization occurs.

To modify the text string in the .mpp file

 * 1) On the file menu, click Open to open the .mpp file that you would like to save to a database in the replica set.
 * 2) On the Tools menu, click Options, then click the View tab.
 * 3) Select the Project Summary Task check box. Click OK.
 * 4) On the Insert menu, click Insert Column. Click the Text2 field name. Click OK.

This places the Text2 column in your current table.
 * 1) Modify the entry in the Text2 column for the Project Summary task so that the DSN and DBQ entries are correct.

DSN is the data source name of the ODBC connection that you want to use. DBQ is the path to the Microsoft Access .mdb file that the DSN uses.

Keywords: kbinterop KB142800

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.