We have seen a number of Enterprise 13 company files come in for data repair over the last month that had corrupted customer credit card information in the file. This kind of data corruption causes the file to fail verify and rebuild and sometimes prevents credit card data from being saved in the file.
In versions prior to 13, we would sometimes see files with corrupted credit card information, particularly if user information in the file was corrupt. But we believe something is different in ES 13, at least through the R4 update. We’re seeing a much higher percentage of files with this kind of corruption.
Almost all of these files have been repairable — we’ve been able to repair the files so that they verify and rebuild without errors and the users can save credit card information afterwards. Sometimes, however, the credit card details themselves are unsalvageable and we have to delete them to save the rest of the file.
Hopefully, the newly released R5 update has addressed whatever the underlying issue is and there will be less of these data integrity issues popping up. We should have a better sense of that in the weeks to come.
I’m cautiously optimistic that when Enterprise 13 comes out, it will fix some of the problems that a number of people are finding in Enterprise Series 12. I’ve talked with a number of clients experiencing…
* Problems in inventory: their file will not verify or rebuild
* Problems in sales orders or estimates: they can’t verify the file or make verified backups
* Corruption in the user list: their file fails rebuild
* Failure when they try to condense their file: condense freezes or gives fatal errors
We can repair the vast majority of these files, but it ain’t easy sometimes. Some of these problematic files are 3GB+ or have a kazillion inventory items and/or lots of corrupt assemblies.
Some of the files that clients are sending us to be supercondensed won’t verify and/or rebuild when they are sent in. We have to repair them first to get them healthy enough to work with.
Seems to me that there shouldn’t be this many files with these kinds of problems. We’ve been in the accounting data consulting business for a long time — since the 80s — and have seen and repaired thousands and thousands of sets of damaged accounting data. But it’s been awhile since I’ve seen a version that has clustered so many data integrity issues, many more than we saw under ES 11 or 10. (Actually, old version 6 had a ton of problems too; that was the first version that used the new underlying database system.)
So I’m keeping my fingers crossed for a lucky Enterprise 13, and wishing the best for Intuit’s development and testing teams…
Other consultants and QuickBooks advisors, what do you think? Does ES 12’s stability seem about the same to you as prior versions? Or a bit more problematic?