Is Your QuickBooks Desktop Sick?
- TracyCooperCPA
- Jun 30
- 2 min read
A client called me because transactions they'd just entered were vanishing. Then their QuickBooks Desktop file stopped opening for some users. Then simple tasks that used to take seconds were taking forever.
Their first thought was "QuickBooks is just glitchy." It wasn't. Their file had a hidden problem that had been building for months, and nobody knew to look for it.
Here's what surprises people: I see this most often in the largest QuickBooks Desktop Enterprise companies, not the small ones. And those are exactly the companies that assume they're the most protected, because they have a real IT department and solid network infrastructure. More users, more network traffic hitting the file day in and day out, and it tends to creep in unnoticed until it's a real problem.
Fixing it took six weeks of manual recovery work. Their team was doing double and triple the work just to keep the business running while we sorted it out, on top of everything else they had going on.
The cause traces back to a file most people have never heard of. Every QuickBooks Desktop company file has a quiet companion file sitting in the same folder, called the .TLG file (short for transaction log). QuickBooks uses it to record every change as a backup, before it's even saved into your main file. It's supposed to stay small, roughly 5% or less of your company file's size, in my experience. When it grows out of control instead, that's a sign of network instability or backup gaps underneath your numbers, and it shows up exactly the way it did for my client: missing entries, files that won't open, everything running slower.
If you're running QuickBooks Desktop Enterprise on a network with multiple users, here's a two-minute check before your next close: open the folder where your company file lives and compare your .TLG file size to your .QBW (company) file size. If it's anywhere close in size, that's a conversation with IT today, not next quarter.
Good IT and a good network don't make you immune here. Intuit won't flag this for you either way. Your file just gets worse until someone finally notices, usually at the worst possible time.
Comments