I have a requirement for three different database access mechanisms.
A Collection db for field use which collects and sends data to the server but does sync from the server to the mobile.
A Viewer db which syncs all data from the server but cannot change or delete records
A Management db which can both read, write and delete records and syncs both ways.

Ideally this would be a single db with different login ID, but…

I looked at the business rules section of FMSync and it seems to deal only with pull.
So based on login, I could use it to block pull of all data for Collection db, or I though perhaps use
appropriate privilege sets to differentiat the three types of access, but I am not sure that this works.

So I tried something a little unusual.
I created a set of both ES_ and ES_PUSH_ instances of my tables in the server.
For Collection db I just have ES_PUSH instances and for the Management db just have ES_ instances.

This works nicely with one exception.

When I create a record in Collection, which then nicely pushes the record to the Server. 
Then when I go to look at that record with Management db and sync with the Server
the record from Collection does not appear.  If I use SyncUtil Script and
Reset ES_UTC_Time in the Management db then all the records
from the Server sync correctly including the record posted by the Collection db.

The problem is that as the db grows downloading the entire db for review instead
of a more normal incremental update will take too long.

So, the question is why is this reset required.  
It is almost as if the time stamp ES_UTC_Time data remains in the ES_PUSH_
table instances instead of becoming part of the original table.

Server db

Collection db

Management db

Any Suggestions are most welcome

Thank you

 

Noticed that a record created by the Field db on iOS sync'd without problem to the Management db on the Mac...  uhmmm...  memories of a method used to solve the round trip problem.  Perhaps that is what I am tripping over.