Hi Chip, That is an interesting idea. It's overkill in this case though. The basic idea is that the Main database is the one actually doing all the work and the Satellites are just doing queries and displaying results. So it's not actually a mirror so much as a reflection, to get a little Platonic <http://decodedpast.com/platos-argument-art-imitation-imitation/2990> here. Frankly setting it up on 4D server would be the optimal solution now.
This whole situation makes the most sense if you imagine yourself doing this project in about 1993 and you don't really need the cost of a full blown server so you think, "you know, I could just take what I've got, strip it down to just do searches and show the results and just use the same data file..." Because that's exactly what it is. On Mon, Dec 5, 2016 at 7:12 AM, Chip Scheide <[email protected]> wrote: > Kirk, > I haven't seen anyone mentioning this.. > As I remember (I do not work with remote sites, so grain of salt..) > - You can turn on data logging (backup) which creates a journal file > that can be used to update a database in case of crash and data loss. > - You can save these files, and pass them to the remote sites for > integration. I think you can automate this process. > > This maybe the same idea implemented automatically by 4D, I think you > can turn on Mirroring, which will auto update a second database with > the 'primary' database's information. I further believe that you can > setup more then 1 mirror. In the situation you are talking about the > mirrors would be the remote site(s) -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
