Losing records with replication scheme.

[sap2]

Scenario:
System data changes at least once per week. Multi users can change data any
number of times.
I have a Design Master(DM) that is a BE that accepts the data (table)
changes which I control.
There is a Hub replica of the DM on the local server.
There is a Server replica of the Hub with FE (doesn't get used much, too slow)
Each user has their own replica (Rn) of the Hub on each laptop (8) and FE
linked to the respective replica.

The logic I used when this was set up was that each user could take their FE
with them (they can choose to connect or not) and then sync directly (in both
directions)with the Hub when in the office. Basically they could work
independently of the server then downlad their updates and get new data when
they connected.

What I think is happening is that when I run the updated system data I have
to change tables (Data) in the DM then sync with Hub. Another user may have
made changes to an existing entry (prior to the system sync) then sync with
the Hub (bi-directinally) and lose the data that they had entered. No
conflicts are logged that I can find.

I am looking for suggestions on how to best fit my needs. I realize that
this may not be the best way and am open to alternatives. The basic result
needs to be that the user can share updated records with the Hub AND receive
new (added) information at any time without losing anything in translation.

Thank you in advance.

 

[sap2]

I did a test and found that when I update the data in the DM I delete a
table then import the new one into the database and then make it replicable.
I guess this resets the table in comparison to the other replicas and that is
why the data is getting overidden.

So my question would be how to add the new data (which the users need) in
the DM without creating a new table or interrupting the replication link to
the original table?