Hi Randy,

THANK YOU!!!!

This scenario is kind of what I was anticipating. Your comments have really 
helped flesh-out my plans.

Regards,

Ken

> On Oct 1, 2018, at 6:35 PM, Randy Engle via 4D_Tech <[email protected]> 
> wrote:
> 
> Ken,
> 
> Sound like a worthy project!
> 
> We do this in our system.
> We use SOAP for the connection
> (cause it's an old system, before Objects and Http Request in 4D)
> 
> NOTE:  You should use "Alpha" fields as your ID fields
> Have each remote use their own Alpha-Prefix for the field value
> 
> This is an "EXTREMELY" shortened summary
> 
> The "Remote" systems are the same structure as the "master" System
> 
> 1.    Create a table:  e.g. [Synch_Records]
> 
> 2.    As record on the "Remote" system is saved
>       In the Trigger (could be otherwise)
>       Determine all fields in the table that have been modified
>       Store an array of field Numbers in the Synch table
> 
> 3.    Upon connecting to the "master system" network
>       1 Synch record at a time (in case of disconnect)
>       Get the field values of the record for the field numbers stored
>       Pack it all into a BLOB  (or Object)
>       a.      Record ID Number
>       b.      Table Number
>       c.      Array of field Numbers
>       d.      Array of Field Values
> 
> 4.    Lookup the table/record Id in the master system
>       Update the master system record (or create it)
>       Send a confirmation to the remote that this record has been updated
>       Set a "complete" flag on the remote system for that record
>       Rinse and Repeat
> 
> 5.    You could do this for records coming from the Master to the remote as 
> well.
> 
> Randy Engle, Director
> XC2 Software LLC – XC2LIVE!
> 
> -----Original Message-----
> From: 4D_Tech <[email protected]> On Behalf Of Kenneth Geiger via 
> 4D_Tech
> Sent: Monday, October 1, 2018 5:00 PM
> To: 4D iNug Technical <[email protected]>
> Cc: Kenneth Geiger <[email protected]>
> Subject: Thoughts and Suggestions?
> 
> Hi All,
> 
> I’m in the initial stages of discussing a potential new 4D Database with a 
> client. It will be Client/Server (5 to 10 users) in a Mac environment. The 
> issue is that they will have people working outside in the woods  where they 
> are virtually guarantied not to have Internet access via cell-service or 
> otherwise. These people need to take notes and record data during their 
> field-work using iPads. Then, once they get back to “civilization”, this data 
> needs to be uploaded to the Database. Obviously, they would not like to have 
> to re-enter the data. Any thoughts or suggestions on how to structure this 
> and/or what tools might be employed would be greatly appreciated.
> 
> TIA
> 
> Ken Geiger
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
> 
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to