Common issues in Quickbooks
-
In the MSP world, often enough we are called upon to ferret out issues with Quickbooks, including ancillary third-party plug-ins.
What have been the worst issues you've been called upon to resolve?
I think the most frustrating ones to troubleshoot are the error codes that stem from multi-user access. -
The worst issues were the networking problems in 2006 when they replaced the DB. I think they have that mostly sorted out now. The other most common issue is data corruption. Source: worked in QuickBooks Enterprise support
-
@Katie Common issues with Quickbooks include turns package over and reads features list.
-
I think it gets tangly when you have a support client with company files that span several different versions.
-
@Katie terminal server comes in handy for that
-
@Nic That client has separate installs for each version. I'm glad I don't work there in accounting. It's enough to make my head spin.
-
@Katie I don't know how to use them but compared to how different people review them and explain them, Peachtree sounds far more robust albeit having a smaller user base compared to QB.
-
@ajstringham They have that, too. At least a dozen different accounting software versions/types.
-
@ajstringham cause they have the accountant market wrapped up. sysadmins have no choice but to go along.
-
juat setup my in laws clothing store with qb pos and accounting. Te flawless integration was anything but. And the support for their pos product is turrible. There are only 5 US based guys the rest are outsourced and reading scripts. Just frustrating.
-
@Nic That sounds like a lot of software out there. It got in early and even though it's past prime it's so entrenched it's going to take time.
-
@ajstringham the codebase is like 25 years old, so that makes it hard too. It was only in 2006 that they went to a SQL database.
-
@Nic What was used before?
-
@ajstringham some old flat file database called c-index or something like that. That's the reason QB is so slow.
-
@Nic Is or was or ...?
-
@ajstringham that's what they used before moving to SQLAnywhere (Sybase's embedded database). The problem was they had all this legacy code, and the only way to get it working at first was to do an emulation layer to duplicate the c-index interface. They've been slowly removing that and talking to SQLAnywhere directly, but that takes a lot of time.
-
@ajstringham the move did speed things up somewhat, and allowed for larger list limits. I haven't played with the last couple years versions so not sure how much faster it is now.
-
@nic Ok, that's quite interesting. It does explain a lot...
-
Going to an embedded database still holds it back a lot. At least in how they use it.
-
@scottalanmiller yeah, but they'll never go to allowing the option to use your own DB.
