August 2015 In Brief

8016. Continued work on the Labelwriter 2015 upgrade.

8031. Completed the programming aspect of the Labelwriter upgrade.

8042. A Printwiser client running two different databases simultaneously reported an issue and we held WhatsApp trouble-shooting chats to determine cause, which eventually turned out to be corruption in the first database. Created the installer for the Labelwriter upgrade, uploaded it to our website and emailed client the download link.

8053. Prepared the documentation for the Labelwriter upgrade. Printwiser client sent the files for their bad database via Dropbox and these were examined and a recovery solution arrived at. Began recovery work for the database.

8064. Visited Labelwriter client to install the latest upgrade, as well as look into some Printwiser user issues.

8075. Visited EPPMS client to resolve an issue preventing the application from starting successfully. Back at the office, evaluated Teamviewer 10 on two internet-connected computers and was impressed to see how the remote control, file transfer and chat features worked.

8090. Recovery of the client’s first Printwiser database was completed. Their version of Printwiser was run against the database to verify all was well.

8123. Client brought their computer to us for the installation of their recovered Printwiser database.

8134. Printwiser client reported a couple of issues and one was resolved by using Teamviewer to remotely examine their computer. The second issue turned out to be as a result of their second database being corrupted. They sent the database files via Dropbox and accelerated recovery was performed. For this purpose our TrimLogSQL utility was created to drastically reduce the size of SQL code produced from the database log file, to reduce processing time. It was able to shrink a 700MB file down to only 180MB. The recovered database was tested and then an installer was created and uploaded to our website for download by the client.