In order to add new functionality and enhance the OA LodgeMaster Offline Client, database changes must be made. After these changes are made, an installed versions of the offline client must be updated, which includes clearing the offline database and reinitializing it, then downloading a copy of your council's database again. Before installing a new version of the offline client, maybe sure the old version has been fully synced so no data is lost.
To provide better support and allow us to make continual improvements, after there is a new release of the offline client that contains database changes, older versions will only be supported for a period of 3 months. This will allow plenty of time for all users to synchronize their old offline install then download and initialize the new version. After 3 months, older offline versions will no longer be able to synchronize and all data changes made offline will be lost. Make sure to update your offline version as soon as new major releases are made.
The chart below identifies major version of the OA LodgeMaster client that have contained database changes, when they were released and when they will no longer be supported - their end of life (EOL) date. As of the EOL date noted versions will no longer be supported. As a note, the LodgeMaster team only provides updates and fixes to the current version, not any previous versions including those that may still be supported for synchronization offline.
When a OA LodgeMaster offline lodge client release reaches End of Life it will no longer sync with the online Lodge Client and will not be supported by the OA LodgeMaster team. Any changes made offline line will be lost and will need to be re-done in the online client or a newer version of the offline client.
Offline Client End Of Life Status
|Offline Client Versions||Release Date||End of Life Date|
|4.0.0 - 4.0.2||April 17, 2018||January 3, 2019|
|4.1.0 - 4.1.2||October 2, 2018||March 27, 2019|
|4.2.0 -||December 27, 2018|