Time Machine saved me again!

I’m quite religious about my backups, but luckily haven’t had to use them except for a whole hard drive failure several years back. However, today, QuickBooks 2007 for the Mac ate my data file and required me to use Time Machine again. I lost 1 invoice and 1 payment which I just entered, so restoring wasn’t bad. This is twice in 1 week that I’ve had to use Time Machine. I’m glad it is there, but am a bit nervous that I’ve had such bad luck this week.

Furthermore, QuickBooks has some problems with Cocoa bindings as demonstrated by an error in the console log:

2/2/08 7:03:18 PM QuickBooks 2007[36756] An instance 0x17820a30 of class QBCompanyFileDoc is being deallocated while key value observers are still registered with it. Observation info is being leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here’s the current observation info:
(
Context: 0x148b42a0, Property: 0x179987a0>
)

I ran into this the other day with ReceiptWallet, but using my binding debug object, I was able to solve it. I guess Leopard got more strict on things like this and is now logging errors. Will Intuit fix this and make QuickBooks more stable? There was recently reported a huge data loss issue with the product which I didn’t think affected me. I hope this isn’t another data loss issue. Of course, I can’t reproduce it (nor would I want to), so reporting it to Intuit is probably useless.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.