Why put up the data off site then now that you know it is a kluge?

Ever considered this if you have to have two?

http://www.techrepublic.com/article/how-to-set-up-database-replication-with-mariadb/

I would only have one single database server for the client myself and if

they have such poor Internet then I'd do it local. All that extra

spaghetti to keep it local and sync it sounds like a wart that will only

grow over time.

On Wed, Jul 12, 2017 at 1:11 PM, <

mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:

> On 2017-07-12 14:05, Stephen Russell wrote:

>

>> How do you modify the timestamp in local mode, or what constitutes a

>> change

>> that you would change the local and not update the backend instead?

>>

>

>

> You wouldn't change the local only; all changes would be done on the

> remote first and then copied locally. That's what I meant when I said "Any

> new adds or updates to existing records will then be done to the remote

> database and then echoed locally."

>

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/CAJidMYK9aKzopAEbfrnMwLduQWEBJhtwGXoCXk_G4F1MgCX=gQ@mail.gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.