Forum Moderators: open
The principle is you set the remote server as master, you then set up the local system as a slave. The master creates binnary files that record changes. The system is then able to see differences between the master and slave and will replicate any changes.
Mack.
Replication is fine but it does have it's draw backs.
What you may want to consider is a simple backup / dump script which you can run, say every 24 hrs.
1. Server DB runs a backup script via cron job overnight and zips it.
2. Each morning windows PC downloars the zip file
3. Windows database is dropped and reloaded with the backup data.
It all depends on the size and frequency as to which method is the most practical.