In R5, when setting $ConflictAction = “1”, the document was handled by field wise replication, i.e only those fields changed since last replication were replicated. In R6, it works the same way (of course)but if I ADD a field to a document, the complete document seem to be replicated.
This has a bad impact when you have a lot of docs, and you need to add a field due to a design change or some agent running. The replication load on the WAN is suddenly way higher than it should be.
Is this documented to be like this somewhere, or is it a bug? Has anyone else discovered the same problem?
Way to test: Simple DB with one form containing a text field and a RT field, set the form to merge replication conflicts. Add a number of docs, including attachements. Create a replica. Use XP client task manager (or win2003) to detect network load. Now change the text field in some docs and replicate. Check the replication load during the session. Add a field to the form, enter some simple data and replicate. The data load will be much higher, since it now includes the attachements field.