QuickBooks Shuts Down When Issuing a Build
A user of CCRQBOM contacted us to report a problem when issuing a build transaction, where the build seemed to complete properly in CCRQBOM, but then QuickBooks would want to shut down without the build being recorded in the company file. After examining the file, we found that it was an error in QuickBooks itself.
Here is the error that displayed in QuickBooks:
What we found was that the bill of material for the assembly item that was being issued had blank lines in it.
Once that blank line was removed, the build could be issued. Select the line and press ctrl-DEL.
It is important to note that the error also occurred when you issued a build in QuickBooks.
This occured in a copy of QuickBooks 2009. It is not clear what revisions or editions show this – we converted the file to QuickBooks 2010 and the error did not occur. Note also that the error doesn’t occur with every assembly that has this problem. However, every time it did occur, we found this problem, and correcting the problem fixed the crashes.
In some cases when you edit a bill of material in QuickBooks you will get this warning:
Check to make sure that all components and the assembly have valid accounts set up. If you have this kind of error in an assembly item, you may not be able to build it in CCRQBOM.
Category: CCRQBOM
About the Author (Author Profile)
Charlie Russell is the founder of CCRSoftware. He’s been involved with the small business software industry since the mid 70′s, focusing on inventory and accounting software for small businesses. He is a Certified Advanced QuickBooks ProAdvisor and participate extensively in the QuickBooks Community user forums under the ID of CCRussell.
Subscribe
If you enjoyed this article, subscribe to receive more just like it.
I have also experienced this error in QB Enterprise 8, and didn’t discover how to fix it until recently, by trial and error. However, I didn’t know about clicking on the line and pressing ctrl-del. It’s good for all inventory users to know about this bug and I, for one, never thought to report it!
Good to know that the upgrade to 10 “should” fix the bug!