My yard was full of robins this morning. A post-Easter bunny rabbit was snuffling around and grazing on new spring growth. The aspen trees are about to display their caterpillar-like blooms. I love all that.

And I love it when QuickBooks seems responsive and energetic when I run a report or pull up a customer’s details. It’s like…springtime in accounting-land!

But what if QuickBooks seems caught in an icy grip? Has QuickBooks ever frozen up on you? It has to me.

There are a number of things that can make QuickBooks freeze.

Complex processes. If QuickBooks is working on something complicated, like rebuilding a file, creating a portable copy, or filtering a big report, it can seem to freeze up. You might see the anxiety-inducing “Not Responding” message at the top of your QuickBooks window.

This is a temporary freeze and nothing to worry about. It’s like a Colorado spring snowstorm. You wait it out; it will be over and gone soon. Go get a cup of coffee, and probably by the time you get back, QuickBooks will have finished its work. Everything will be back to normal.

I wish that the Intuit development team would put up a message in QuickBooks that would say “Processing, please stand by…” to lower the anxiety of bookkeepers staring at that “Not Responding” message…

RELATED: What to Do When QuickBooks Is (Not Responding)?

Big databases. Big files can make QuickBooks seem to freeze even for non-intensive tasks, like saving an invoice.

What is big, you ask? Well, for Pro files, maybe 200MB. For Premier files, perhaps 350MB. For Enterprise files, perhaps 1.5GB. But the proof is in the pudding: your file may be getting on the big side whenever it starts to become sluggish or unstable.

When your database gets large, then some of the processes in QuickBooks have to crank through a lot of information to deliver accounting results on your screen. The bigger the file, the more the information it has to sift through, and the more time it takes. That can make it seem to freeze.

The solution? You can upgrade to Enterprise, if you are using Pro or Premier now. Enterprise is more robust with larger files.

You can also put your QuickBooks files on a SSD drive, which reportedly can speed things up.

Or you can have your existing file supercondensed, which makes it smaller, faster, and more stable. You can try the built-in condense command too, but results vary there, so make sure to try it on a copy of your file first, not your live file.

RELATED: Interview/case study: User with Big, Slow QuickBooks File

Corrupt data. This one sounds scary. Who wants to contemplate the possibility that the lifeblood file of their business might get corrupted?

But QuickBooks files, like any complex file, can get corrupted by a number of things. When that happens, one of the symptoms may be that QuickBooks freezes when you try to do certain things. It may freeze when you try to go into a certain screen, or look at a particular piece of information.

RELATED: What Damages QuickBooks Data Files?

If Quickbooks freezes because of data corruption, the obvious solution is to restore your last good backup. Especially if not much work has been done in the file since that backup was made.

If that is not possible, then data repair services are available, and downtime should be minimal.

RELATED: Can a Corrupted QuickBooks File Be Recovered?

Has QuickBooks ever frozen up for you? How did you thaw it out?

Please follow and like us:

2 thoughts on “It’s Springtime, but QuickBooks Seems to Be Frozen

  1. One thing i realized is that when using a multi-user license and another person is already logged into a file that I am trying to open I get a message stating the file cannot be opened. The reason this happens is because the last time I used the same file I switched to single user mode and forgot to switch back to multi-user mode. Once the other user is logged out I can then go into the file. Once I’m in the file I switch back to multi-user and I no longer have that issue.

    Reply

Leave a reply

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> 

required