As a rule of thumb When designing a Replication database system I try to keep table data changes to a minimum. This has meant only updating changed rows, adding new rows or removing deleted ones. All of this in the design master/replication master.
Will column changes as opposed to row changes allow me to abandon my rule of thumb and use an update query to overwrite all rows, mostly with the same data and will the replication process know that the overwritten data has remained the same or will it cause
it to be logged as changed thereby increasing the size of the MDB.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.