How OnWeb Synchronization and Sessions Work

Updated 2009-12-01 | Filed under OnWeb | PDF

Synchronization

When you first use EQL Synchronize on your Access Database the plugin goes through 4 steps: export, push, pull and import.

1. Export

The MS Access Database plus any existing data links are read and re-written to your local disk in EQL compressed format.

Export

2. Push

This data is then pushed to the OnWeb server. The server merges any changes with the existing file on the server. This includes merging changes with changes made by other users. During the push a new .mdb file is created on the server. This .mdb file is used for future OnWeb sessions (explained below).

Push

3. Pull

Any changes generated on the server are merged into the locally generated (during export) EQL compressed files.

Pull

4. Import

EQL compressed files are integrated into the original Access database.

Import

OnWeb

1. Start a new OnWeb session

The RFB (remote framebuffer) protocol in combination with a flashviewer is used to display the Access database in a browser. The .mdb file that was created is used to display the database.

2. Close the OnWeb session

If the OnWeb session is closed with 'save-on-close' set to True it will export and push its changes. Recall that the push will also re-create the .mdb file on the server, which will then be used for all future OnWeb sessions. If the save-on-close is set to False it will discard any changes when the OnWeb session ends.

Related Articles

Unrelated Articles