EZSync Cloud Edition

From $1

1. ezsync-server.exe
2. EZsync3.exe

This syncs a local EZdata database with a cloud based Synapse Server - though the Synapse Server could as well be anywhere with an internet connection.

There is a user defined poll period after which it repeatedly scans the ezdata db.
If any patient records are found where the changedate <> synapsedate, and changetime <> synapsetime, and the changedate is later, then an addupdate record is sent out ( the synapse* fields are created by the EZSync client )
This record is now updated so that synapsedate and synapsetime are set to the change* versions. This prevents the sending out of duplicate messages
The cloud server reads this message, and updates the patient in question.
A response is sent back indicating success or not.
If not, the changes are not rolled back, but an error is flagged. If we rolled the changes back, then the same message would keep being sent

ezsync-server.exe

This is the server application, which is console based and gui-less. It runs on the PC where the Synapse-server and database reside. Place it in a directory called c:\ezsync.

It needs a configuration file named ezsync-server-config.r in the same directory which looks like this:

#[object! [
    ezdata-path: "C:\ezclaim\EZData.mdb"
    synapse-dsn: "demo"
    acid: "???"
    awsak: "ASASGWERWRWAGAF"
    awssk: "ERWER#$%@#GDGWERTW#%#$%GSWERGDGSERTE"
    toq: "toec2"
    fromq: "fromec2"
]]

synapse-dsn is the ODBC dsn to the synapse server database
acid is not used yet
awsak is your Amazon access key
awssk is your Amazon secret key
toq is the name of the SQS queue used to send messages from the client to ezsync-server ( just use the same name here "toec2" )
fromq is the name of the SQS queue used to send messages from the ezsync-server back to the ezsync client ( use "fromec2" )