Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 172164 - Last Review: January 20, 2007 - Revision: 3.4
ACC97: Data in OLE Object or Memo Field Missing from Replica
This article was previously published under Q172164
Moderate: Requires basic macro, coding, and interoperability skills.
On This Page
SYMPTOMS
After you synchronize a replica, the data in a Memo field or OLE Object
field in a member of the replica set is missing. Also, a conflict error is
generated.
CAUSE
During synchronization, an error occurred, which prevented the transfer of
data in a Memo field or OLE Object field to one of the replicas.
RESOLUTION
To correct the conflict error and restore the data to the Memo or OLE
object field, follow these steps:
- Open the replica that contains the conflict table. In the Resolve
Replications Conflicts dialog box, click Resolve Conflicts. This button
is not enabled unless you have opened the replica containing the
conflict table.
- Note that the existing record contains data in the OLE Object or Memo
field, and that the Conflict record does not contain data in that field.
Click Keep Existing Record.
- When prompted to confirm that you want to keep the existing record,
click Yes. When you receive a message that you've successfully resolved
all the conflicts, click OK.
- In the Resolve Replication Conflicts dialog box, click Close.
- Synchronize with the other member of the replica set.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Access 97. This
problem no longer occurs in Microsoft Access 97 Service Release 1.
NOTE: Stand-alone Microsoft Access 97 Service Release 1 is not currently
available, but you can update your copy of Microsoft Access 97 to Service
Release 1 by downloading Microsoft Office Service Release 1 from
Microsoft's Web site at:
MORE INFORMATION
Steps to Reproduce Problem
- Start Microsoft Access and open a new, blank database.
- Create a new table named tblTest:
Table: tblTest
-----------------------------
Field Name: ID
Data Type: Number
Field Size: Long integer
Indexed: Yes (No Duplicates)
Field Name: Notes
Data Type: Memo
Table Properties: tblTest
-------------------------
PrimaryKey: ID
Close and save the table as tblTest.
- Create a replica of the database.
- In the Design Master, enter the following record into the tblTest
table:
ID Notes
------------
1 test
Close the Design Master.
- Open the replica and enter the following record into the tblTest
table:
ID Notes
------------
1 test
- Synchronize with the Design Master.
- In the Resolve Replication Conflicts dialog box, click View Data
Errors. Note that the changes you requested were not successful
because they would create duplicate values in the index, primary
key, or relationship.
- Close the Replication Data Errors dialog box and close the Resolve
Replication Conflicts dialog box.
- Close the replica and open the Design Master.
- When the Resolve Replication Conflicts dialog box appears, click
Close.
- Open the tblTest table and change the one existing record as follows:
ID Notes
------------
1 test
- Close the table and synchronize with the replica. Note that there is
now a replication conflict in the Design Master.
- Close the Resolve Replication Conflicts dialog box and open the
tblTest table. Note that both records contain data in the Notes field.
- Close the Design Master and open the replica. Open the tblTest table.
Note that in the second record, there is no data in the Notes field.
REFERENCES
For more information about resolving replication data errors, search the
Help Index for "replication, troubleshooting," and display the topic
"Resolve replication data errors."
APPLIES TO
- Microsoft Access 97 Standard Edition
| kbdownload kbbug KB172164 |
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please