Live Database System

[chri55w]

In order to maintain data integrity and sync all employee time log data to one location the application should use an online database where possible to store all data, the Import functionality should be removed to an external application which will not be needed by most users. a Local database will be used for offline interaction, this will fetch all the customer, service item, class, employee and TimerType data when connected to the live database and only temporarily store Time Logs when the user cannot connect to the Live Database

[BradConnor]

Looks OK!

[chri55w]

Database has been created, Import application has been completed, Documentation to be provided within the WIKI.

Making changes to the Timer application to access Live Database before creating the Local Database and working with syncing functionality

[chri55w]

Database connections working, Importing data functions completed. Old import code removed and start-up process stripped to basics fetching all live data from database.

Created this UML Activity Diagram to help visualise the desired start up process

[chri55w]

Further Complications / Ideas have prompted me to look at some Data restructuring to avoid wasted space and improve maintainability.

Database Changes

Application Start Up Process Plan

These changes are priority and will be implemented as soon as possible

[chri55w]

Given the size and complexity of these changes a lot of features have been disabled temporarily. That being said the remaining functionality has now been modified to work as designed with the Live and Local Database.

This issue will now be closed and replaced with several new issues to better log the Disabled features that must be re-enabled.