During replication, since it occurs at a very low level in the data engine, there is no way to know what the “progress” is. For example “Records in selection” will only return the total before or after replication depending on when it is called; it will not increment as the replication progresses.

For this reason a progress bar cannot be effectively used to represent the progress of a replicaton call. Consider using a thermometer instead while replication occurs if you with to display a message for the user.

Note: it is worth mentioning that replication should occur as often as possible so as not to force the user to wait. Because replication occurs at such a low level in the database engine, most data access is locked. The fewer the changes to send, the faster the replication will be so do it often.