CCRQBOM can generate a requirements list, a report that shows what items you need to purchase if you want to build a required quantity of an assembly. I’ll show you how to add some calculated fields to the report to provide total shortage cost calculation.
If you have a “card reader” on your system you may get a Windows error message that pops up when you start certain programs (such as the CCRSoftware applications) that is titled Windows – No Disk. You may get this several times in a row before the software starts. Here are some ideas on how to deal with this.
We spent several days working with one customer who could not get multiple level assemblies to build correctly with CCRQBOM. A requirements report would say that you could build, but when the build was issued the program would say that it couldn’t complete the build and would back everything out. It ends up that there is a bug in QuickBooks itself that is causing the problem.
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.
All current releases of CCRSoftware products do work with QuickBooks 2010 without any problems, but the intial releases of the new version of QuickBooks has a number of bugs that are causing some people problems with some third party products.
One element that can make a printed invoice easier to read is to print every other detail line with a different background color or shade, so that it is easy to distinguish between the detail lines. This feature can be added very easily to CCRQInvoice form templates, as we will show you in this article.
We have just released an update to CCRQBOM. If you are using version 3.2.1 then please download the latest version, 3.2.2, from our web site (go to http://www.ccrsoftware.com/CCRQBOM/CCRQBOM.htm and click on the “download free trial link).
This release modifies the “Use SubAssembly Balances” feature. In some cases the program was not using all of the subassembly items that were on hand.
We have released a new version of CCRQBOM. If you have a registered copy you can download and install this update for not additional charge.
For a quick overview of the new features, see this article.
The new release adds:
- A Where Used report, listing each component and the assemblies that use them.
- Additional fields to the BOM report so you can do further customization to fit your needs.
- The ability to batch print BOM’s, so you can print any or all assemblies at one time.
- Aggregate Requirements – the ability to include multiple assemblies in the requirements report, so you can see the combined requirements and shortages.
- Multiple Builds so you can issue builds for multiple items at one time.
- Listing all assemblies found in open sales orders, with a requirements list based on this information.
- Pending Builds (if you have a 2008 or later edition of QuickBooks).
- Support for selected Canadian, UK and Australian versions of QuickBooks.
- The ability to take balances of intermediate assemblies into account when building.
You can preview the new program by looking at the online documentation, available at our CCRQBOM web site.
What Is Next?
Now it is time to work on the next release – let us know what you would like to see in the next release of CCRQBOM!
Recently several of our customers have asked if there is a way to add line numbers to their reports. This posting will briefly describe how to accomplish this in both CCRQInvoice and CCRQBOM. We assume that you are familiar with the basics of editing a report.
Just a quick note – several of our clients have noted that they suddenly find that their CCRSoftware product can no longer connect to their QuickBooks company file. The symptoms vary, but the most typical are that the CCRSoftware program says that it Cannot open the QuickBooks Company File, and there often is a mention of an error code, 80040408 (or something similar).
There are two common causes for this, and a simple correction for both:
- Did you just update your QuickBooks program, perhaps with an “automatic update”? If you did, and then you started the CCRSoftware program and got this error, the simple fix is to close QuickBooks and then restart it. For some reasons many of the “automatic updates” close down the feature that QuickBooks provides that lets third party programs to access the file. Exiting and restarting QuickBooks usually resolves this.
- Are you running on Microsoft Vista? Please note that with Vista, all third party products that integrate with QuickBooks require that you enable UAC. If you have disabled this feature in Vista, you will have problems.
I’m mentioning this today because the recent R7 update for QuickBooks 2009 has created a lot of technical support calls for us, for the reason described above.
