Client is £1m t/o wholesaler. Currently has (I think) 5 years of history in the file which has now reached 120MB and causing problems. QB support telling him that they recommend file size no greater than 30-40MB, but that effectively means (at best) only having 1 year of history as well as the current year.
This all seems rather surprising as I wouldn't regard £1m t/o as particularly large, yet following the QB support recommendation means not having available what is QB's best feature (all those reports covering whatever period you want).
Does this sound right? Has anyone else had this experience? Is there a workaround?
Assuming there is no viable long-term solution, has anyone any words of wisdom re good systems to migrate to from QB?
Adam Reeves
Replies (3)
Please login or register to join the discussion.
quickbooks
They certainly are interested in the larger customer, which is why they have an enterprise product in the US, this is priced in the thousands though. Quickbooks and data corruption have always gone together, which is probably why they emphasise data recovery in their support contracts. I have had a few large users with QB data files that have become quite screwed up, fortunately for them we had regular backups to return to and rekeying the data was not too much of a problem. I would encourage all users of all systems to take regular backups, but especially users of Quickbooks with large data files. Plug time** you may want to look at Anagram Encore** if you expect the data file to continue growing stongly.
Yours Viv Burrows
[email protected]
07811 440877
It depends on how the file is used.....
It sounds like the user has either a large volume of transactions or a large number of customers - probably both!
Very large files will slow QuickBooks down - but again this depends on the PC, whether the file is on a network and other factors.
So its not easy to say exactly what size the file should be - but to keep optimum performance under 50mb in most cases.
Best thing to do is see how large the file is after a year and monitor performance. (PCs are getting faster and RAM is cheap...) Also avoid pulling reports that look at large date ranges while users are trying to enter transactions. It's likley that user will be ok.
As for £1m t/o that is only relevant if it means a large volume of transactions.