Have you seen a message in CheckBook or CheckBook Pro about a damaged document or a damaged database?\u00c2\u00a0 Don\u00e2\u20ac\u2122t panic.<\/b>\u00c2\u00a0 We can help you with that. \u00c2\u00a0Please read the rest of this post for details and how to proceed.<\/p>\n
First, unless you’ve been using version 2.5.7 or later for some time, we’re almost positive the damage occurred while you were using an older\u00c2\u00a0version<\/strong> of CheckBook or CheckBook Pro.\u00c2\u00a0 We\u00e2\u20ac\u2122ll explain why and\u00c2\u00a0how the current version won\u00e2\u20ac\u2122t let you down in the same way, but we feel it’s very important for you to know that damaging your document is not<\/strong> the very first thing 2.5.7 will do. \u00c2\u00a0It’s trying to do exactly the opposite.<\/p>\n In versions 2.5 to 2.5.5, CheckBook and CheckBook Pro weren\u00e2\u20ac\u2122t able to detect and tell their user about all the forms of damage that could happen to one of their documents.\u00c2\u00a0 This sometimes led to situations where a document became damaged but was still almost<\/i> usable, and sometimes the application would let you continue using the document without telling you. \u00c2\u00a0This would go on for days or weeks without you knowing the damage was done, until you hit a point where the document just couldn\u00e2\u20ac\u2122t be used anymore\u00c2\u00a0and you’d\u00c2\u00a0either contact us for help or throw the app out the window.<\/p>\n Thank you for not throwing the app out the window.<\/p>\n We’re responsible for not telling you your document was damaged as soon as possible\u00c2\u00a0and we apologize for the grief we caused.\u00c2\u00a0 To ensure this won\u00e2\u20ac\u2122t happen again, and to repair your document in many cases, we made some very serious improvements in version 2.5.7:<\/p>\n If you see a message about a damaged document<\/strong> when you open CheckBook or CheckBook Pro 2.5.7, look at the buttons below the message. \u00c2\u00a0If you see an option to repair the document, try it<\/strong>. \u00c2\u00a0If the document can’t be repaired and you’re given the option to restore a backup, try it<\/strong>. \u00c2\u00a0If at any point you see a bunch of errors about the database, click the OK button, quit and open CheckBook\u00c2\u00a0again, and try restoring<\/strong> instead of repairing. \u00c2\u00a0If you feel overwhelmed by errors and need a hand sorting it out, click the Send to Splasm… button<\/strong> below the errors so we can have a look and help out. \u00c2\u00a0We’d be happy to!<\/p>\n One thing<\/strong> about restoring an automatic backup: \u00c2\u00a0The older the backup, the more things won’t be quite the way you left them. \u00c2\u00a0Any Entries you created since the backup was made won’t be there – and neither will any Scheduled Entries you might have committed. \u00c2\u00a0So you might notice some Entries are missing or Scheduled Entries you already committed appear in the Schedule Reminder. \u00c2\u00a0We wish there was a way around it but that’s just how it works when you restore an older version of your data.<\/p>\n Thank you again for allowing us to explain the changes we’ve made in CheckBook and CheckBook Pro 2.5.7. \u00c2\u00a0Your support is paramount and we’re committed to\u00c2\u00a0doing our best to return that support in kind when you need it. \u00c2\u00a0Please get in touch at support@splasm.com if you need any additional details.<\/p>\n","protected":false},"excerpt":{"rendered":" Have you seen a message in CheckBook or CheckBook Pro about a damaged document or a damaged database?\u00c2\u00a0 Don\u00e2\u20ac\u2122t panic.\u00c2\u00a0 We can help you with that. \u00c2\u00a0Please read the rest of this post for details and how to proceed. First, … Continue reading \n