MOD2000: Adding Publication During Synchronization Causes Incorrect Conflict Resolution Data (244218)


The information in this article applies to:

  • Microsoft Office 2000 Developer
This article was previously published under Q244218

SYMPTOMS

When you are using Access Workflow Designer, if you attempt to synchronize offline changes when another publication has been added to the solution, you may receive the following conflict error message:
Changes to the online database schema have been detected. This row has not been synchronized and may conflict with a row in the online database. Click "Keep Data Locally" to apply your change.
Also, incorrect data appears in one or more fields shown in the message. If you choose to keep the data locally, the data is saved to your local (offline) data store.

CAUSE

Because solution schema changes occur when you add a publication while synchronizing to a different publication, problems occur when parsing the INSERT statement or statements, and some columns and their related data may not be displayed properly.

RESOLUTION

To resolve this problem, obtain Microsoft Office 2000 Developer Service Release 1 (SR-1).

To obtain SR-1, click the article number below to view the article in the Microsoft Knowledge Base:

253566 MOD2000: How to Obtain and Install Microsoft Office 2000 Developer Service Release 1 (SR-1)

To temporarily work around this problem, do not create another publication while attempting to synchronize. If you do create another publication while attempting to synchronize, you will be unable to connect to the online data store and work online until the conflicting data is deleted from the local (offline) data store.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.  This problem was corrected in Microsoft Office 2000 Developer SR-1.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Install all supporting software on a Microsoft Windows NT Server computer, including the Access Workflow Designer server components.
  2. Install the Access Workflow Designer developer components on a Microsoft Windows 98 computer.
  3. On the server computer, deploy the Issue Tracking application.
  4. On the client computer (running Microsoft Windows 98), start Microsoft Internet Explorer.
  5. On the Tools menu, click Internet Options.
  6. Click the Security tab.
  7. Click Trusted Sites, and then click Sites.
  8. Click to clear the Require server verification (https:) for all sites in this zone check box.
  9. In the Add this Web site to the zone text box, type the following address

    http://server name/Issue Tracking database name/default.htm

    where server name is the name of the server in step 1 and Issue Tracking database name is the name of the Issue Tracking database that you deployed in step 3.
  10. Click OK twice, and then quit Internet Explorer.
  11. Start Internet Explorer, and go to the following address

    http://server name/Issue Tracking database name/default.htm

    where server name is the name of the server in step 1 and Issue Tracking database name is the name of the Issue Tracking database that you deployed in step 3.
  12. Create an issue and save it.
  13. Click Offline, and then click Synchronize.
  14. Minimize the Issue Tracking window, and then start Access Workflow Designer.
  15. Create another publication named Test in the Issue Tracking database.
  16. Wait until both the Test publication and the synchronization are finished.
  17. Go back to the Issue Tracking window. On the File menu, click Work Offline.
  18. Create one or more issues (offline), and then save them.
  19. Click Offline, and then click Synchronize.

    Note that you receive the conflict error described in the "Symptoms" section.
Also note the data and the column that the data appears in. Note that the data appears in the wrong column. For example, the date that the issue is due appears in the Subject column.
Modification Type:MajorLast Reviewed:9/3/2002
Keywords:kbbug kbWorkFlowDesigner KB244218
©2002 Microsoft Corporation. All rights reserved.