QuickBooks

QuickBooks 2013 R6

Written by Charlie Russell

Intuit has released the QuickBooks 2013 R6 update for the U.S. version of QuickBooks. This is available as a manual update from the Intuit support web site, and it looks as though Intuit will push this out as an automatic update right away also, rather than a week later as is normal.  Please note that at the time this is being posted I have not worked with this release extensively.

This is a big maintenance release, with changes to the user interface, fixes to random crashes, improvements with PDF support, a fix for the Windows 8 scan manager, and lots and lots of bug fixes.

There has been a growing number of reports of problems with QuickBooks 2013 R5 (and earlier revisions), but I have had a hard time pinning down what exactly has been going on. I’ve had two problems evaluating this:

  1. My own installation of QuickBooks 2013 hasn’t shown any of these problems. Mine doesn’t crash! If I can’t duplicate a problem, I can’t figure out what the issue might be.
  2. Many of the reports have been too generic to be able to pin things down. “QuickBooks crashed” – without saying what exactly the error message was (if any), or what exactly you were doing at the time.

Looking at the release notes for 2013 R6 I can see that there were a lot of different reasons for crashes scattered about, which was part of the problem in pinning things down.

So, has Intuit fixed all the problems in QuickBooks 2013 with the R6 release? Who knows? I can’t answer that, all I can do is point out that there are a heck of a lot of problems fixed in this release.

So, let’s take a look at what they have done…

Crashes and Database Reliability

There has been a growing number of reports of people unhappy with QuickBooks 2013 due to a variety of errors and crashes. I’m not talking about situations where a calculation is done wrong, or a field is missing – these are situations where QuickBooks will tell you there is an unrecoverable error, and then the program crashes or won’t let you continue. Serious problems, frustrating problems. Since it is very hard to roll back to a prior year of QuickBooks, once you are using 2013 you may have to stick with it, or reenter a lot of data.

The R6 release has a long list of fixes for these kinds of errors. Will this fix ALL of the problems? Probably not, but they have resolved a big chunk of them. Note that I can’t say if these problems are all truly resolved because I don’t have test cases that show many of these errors.

The following “Unrecoverable errors” should be fixed:

  • “Unrecoverable error 02700 80318”  – you might also just see “QBW32.EXE – Fatal Application Exit.”  This is probably the biggest problem that people have been running into, from what I understand. Lots of pain over this one, people should be very happy that it is fixed.  This might have occurred when you have the report center open in the background, but it isn’t limited to that situation.
  • “Unrecoverable error 19975 55647” when you have My Apps open in the left navigation menu.
  • “Unrecoverable error 13968 12568” when opening the Customer Center.
  • “Unrecoverable error 14854 49054” when opening any invoice by double-clicking on it in the Open Invoices report
  • “Unrecoverable error 13968 12922” when opening the Customer Center in multi-user mode.
  • “Unrecoverable error 51609” when setting up new users.
  • “Unrecoverable error 24995” when users minimize/maximize QuickBooks multiple times when the progress bar is on.
  • “Unrecoverable error 17371 39236” when users use “Full Screen Mode.”
  • “Unrecoverable error 20888 41171” when users open a transaction form.
  • “Unrecoverable error 15346 90861” when running the Review 1099 Vendors report.
  • You will no longer see an unrecoverable error when customizing the colored icon bar.

Sometimes you won’t get the error message shown above, instead the program may just randomly shut down. Some of those error numbers might only show in Windows XP systems.

Other crash and similar errors:

  • An issue was resolved that would cause QuickBooks to hang when switching from single user mode to multi-user mode.
  • QuickBooks will no longer close when trying to add a To Do note having more than 500 characters while in multi-user mode.
  • A problem was resolved that would cause QuickBooks to close unexpectedly when pressing the F2 key.
  • QuickBooks will no longer close when you open inventory items from the Inventory Valuation Summary report.

Database Integrity issues are often found when you use the Verify Data  and Rebuild Data utilities. If you can’t verify a QuickBooks company file, you can’t rebuild it or make a fully verified backup. Here are some fixes that relate to Verify/Rebuild (note that some of these deal with the optional Advanced Inventory feature in QuickBooks Enterprise).

  • Verify/Rebuild will not fail if it finds inventory transfers that have all positive quantities in the “from” and “to” fields.
  • Verify will no longer fail after an inventory transfer is recorded while the average cost is negative (see this.
  • Editing the site on a transaction after turning off the bin location feature will no longer cause Verify to fail.

QuickBooks has always thrown too many “event” error messages into your Windows Event Viewer logs, which annoys system administrators (who hate it when you tell them “just ignore that, QuickBooks does that all the time”). Here are a couple of fixes that will help get the system admin off your back:

  • The error “LVL_ERROR-Unable to find the section for this menu item” will no longer appear in the Windows Event Viewer. This error, and other harmless messages, will only appear in the QBWIN.LOG file.
  • QuickBooks will no longer cause server event logs to show an “EventID: 4 entry” for an unexpected error.

Color is Back!

The new user interface in QuickBooks 2013 has been the subject of MANY heated discussions. Some people love it, some people hate it, this probably has been the most discussed change in QuickBooks over the past several years. One aspect of the change was that the ability to select the “color scheme” of QuickBooks was removed. We did get ability to add a colored “company flag” (as well as to select colored icons in the top icon bar) in the 2013 R4 release, but that still wasn’t the same as the older “color scheme” approach.

With this release, color schemes are back!

QuickBooks Color Scheme

According to Pamela Bailey, the Experience Design Leader for QuickBooks (Windows):

“Our teams have been actively listening and understanding the feedback from our customers in order to further refine QuickBooks 2013. In our R6 release, we’re introducing a preference to apply a color treatment to the window frame of all QuickBooks windows (14 colors in total). This update is designed to “at-a-glance” help distinguish company files. Thank you to everyone who has taken the time to share their feedback. We’ll continue to listen to customer feedback to make QuickBooks even better!”

Is this enough to resolve the complaints? I’m not sure, since some of the issues that people have with 2013 has more to do about font sizes and the room it takes to display things. Now that we have color schemes again, I’m waiting for the next round of complaints. The colors are very vibrant – not the subtle choices like “Sea Green” or “Denim Blues” like we had before. Also, this doesn’t affect the color of the left icon bar. However, I do like the option, and it does show that Intuit listens to customer feedback.

One word of caution – before you install this update you may want to check the color that you have selected for the “company flag”. I had “Pink” selected, which made the small “company flag” stand out (and, note, the “company flag” is gone in R6 now). When I updated my file to R6 the “color scheme” stayed with Pink, and it just about knocked me out of my chair when I started QuickBooks and all that color showed up…

Some other user interface changes – in transaction forms they have changed some of the labels to upper case, to make them more easily readable. The top invoice is from R5, the bottom is from R6.

Comparing R5 to R6 forms

There will still be people who are not happy with the new user interface – the lack of color in the left icon bar, the added “white space”, the narrow scroll bars. It is a matter of personal preference – I’ve gotten used to what we have now, it doesn’t bother me any longer (other than those dang small scroll bars). My gut feeling is that this just about the last change you are going to see in the UI…

PDF Improvements

PDF drivers have been a historical nightmare for QuickBooks (see my article on PDF drivers that has a section on the sad history of QuickBooks and PDF drivers, as well as my most recent article on fixing PDF problems). I’m not sure why they continue to use the kinds of technology that they do, since it is a problem every year. In any case, the R6 release has a number of fixes that will improve the reliability of the PDF features in QuickBooks for a number of cases, relating to Windows 8 as well as older versions of Windows. Will this fix them all? I can’t say, but it should be an improvement.

  1. You are less likely to see the “missing component” error when launching QuickBooks 2013. This was due to the XPS printer not being found in the printer list. QuickBooks will now detect if the printer is missing and reinstall it automatically when launching.
  2. You will be less likely to see PDF errors if the print spooler is off. If the Windows print spooler service is stopped, QuickBooks will start it when saving as PDF.
  3. QuickBooks will automatically fix the “unable to print to PDF” error that occurs when the Windows TEMP folder does not have full control. QuickBooks will now add full control to the  temp folder if there are any permission issues.
  4. QuickBooks will now allow a QuickReport to be saved as PDF if the report is blank.
  5. The first time you try to save a report or form as a PDF on Windows 8 you will no longer see an error from QuickBooks.
  6. Previous bank reconciliation will no longer be blank.
  7. The QBWin.log will now show PDF errors! If you are still getting PDF errors in 2013, you can now look in the QBWin.log file for exact cause.

Scanning Improvements in Windows 8

On Windows 8 the scan manager for the Doc Center feature wouldn’t work – and this release should fix that issue. I couldn’t test this myself as I don’t have a scanner that is compatible (and besides, I use SmartVault instead).

Company Information and Subscriptions

If you select Company and then Company Information you can see the information you have set up for your company file – addresses, phone numbers, web sites, EIN, and more. In prior versions of QuickBooks you would see:

Company Information Prior to R6

With R6 Intuit has updated this window significantly. Now you see additional information about your license and the subscriptions that you have.

Company Information Starting with R6

I think that this is an improvement, although it could have been a bit better. Having to scroll through the “current subscriptions” is a bit of a pain – my “Advanced Inventory” subscription doesn’t show when I first open the window, I have to scroll to see it. I think that my current subscriptions should show first, with the “advertising” for other services coming after that. Also, it takes additional clicks to see the “company ship-to address” – why couldn’t it be shown here? In the old system there was one button to click to open a window for that, in the new one I have to open two windows to get to it.

Note that to edit this info you click the edit icon in the upper right – that will open the old style window, which is where you can edit info (and find the ship-to address).

Lots of Bug Fixes, Some Updates

Here’s the rest of the changes – mostly bug fixes, a few things that are improvements. In some cases I am not exactly clear what Intuit is referring to in their notes.

  • Terms on Sales Orders will now flow to the invoice you create from it, rather than default to the terms in the customer record (see this KB article).
  • The Add/Edit Multiple List Entries window will now refresh properly if it is open and you add an assembly item to the item list.
  • Enterprise Advanced Inventory:
    • The inventory Stock Status by Site report will show a “No Site” section for transactions that don’t have a site selected.
    • An issue was fixed where barcode scanners would not work if you had QuickBooks open and you unplugged the scanner and then plugged it back in.
    • If you enable the “bin location” feature, the on-hand quantity of a build assembly will no longer show zero if there are builds that predate inventory transactions.
    • Multi-user performance is improved for large company files that have the Lot Numbers feature enabled.
    • Unit Cost has been added to the FIFO Cost Lot History by Item report.
    • You will no longer get a warning when a duplicate lot number is used.
    • If using the multiple sites feature, you will no longer see a warning when editing a build assembly transaction when the original build quantity is greater than the available quantity.
    • Serial numbers in stock reports will only show the current quantity of an item.
    • Costs on purchase transactions will no longer display incorrectly when the Unit of Measure feature is enabled.
    • The number of rows visible in the Bins tab in the Inventory Center has been increased.
    • Purchase orders and sales orders without an inventory site will now display a quantity on the stock status by site report.
  • Banking: When the sort-by option “Date, Type, Number/Ref” is chosen, deposits will now be listed first for transactions created on the same date.
  • The Batch Enter Transactions menu is now accessible under the Company menu for non-accountant versions of QuickBooks Enterprise V13.0. This feature used to be limited to just accountant versions.
  • To-Do notes will no longer be truncated if the description is more than 100 characters.
  • A problem is fixed where duplicate employee names would appear when picking one on the Add To Do window.
  • The Item Image window in the Inventory Center has been re-sized to support lower resolutions.
  • All new customer information (phone, email, etc.) will be added to any new job created for that customer.
  • Several issues have been resolved that prevented QBB (backup) files created in QuickBooks for Mac from being opened in QuickBooks for Windows 2013.
  • QuickBooks will no longer prompt you to allow the Fixed Asset Manager to access the QuickBooks company file.
  • Payroll help has been updated.
  • This release includes the latest update to Intuit Sync Manager.
  • When the multiple currency feature is enabled, total values will be reflected properly on a purchase order when it is created from an estimate.
  • The Open Form button on the Templates list will now open the highlighted template.
  • You can now use the space bar to select open purchase orders when creating bills.
  • Payroll
    • Pressing the “s’” key on the Employee Defaults window will act as a hot key to select a Class.
    • the performance of the Send Payroll Data workflow has been improved.
    • You will not be prompted to send Direct Deposit for Vendor payments if Direct Deposit for Vendor is not active for the company file.
    • You will no longer see the message “You have Direct Deposit checks to send” when there are no checks to send.
    • Monthly payroll item limits are now supported.
    • After a check is voided and sent to Intuit using Direct Deposit, only a Cleared watermark will be displayed.
  • The max database cache size for Enterprise has been increased to 512 MB for improved performance. See this KB article for a discussion on cache settings.
  • The alignment of a printed Inventory Assembly Bill of Materials report is corrected.
  • The “Fit report to” setting now works correctly when printing memorized reports.
  • You will no longer see “There is Not Enough Memory to Complete this Action” when attempting to deactivate an account set up for Online Banking (see this KB article).
  • The Pay Online option on the Write Checks window will now be enabled in company files with the multiple currency feature enabled, when you are in multi-user mode. This will only occur if your base currency is USD.
  • Clicking the Revert button in the modify report window will now set the Zero Q OH filter back to the default setting.
  • Sales description will now show on all reports except for Purchase reports.
  • A problem was resolved that would show the word “Overflow” on a memorized cash basis custom transaction detail report instead of dollar amounts.
  • Non-site-specific summary reports will now show site date when the report basis is set to Accrual.
  • QBSDK applications will now be allowed to run in “unattended mode” without receiving script errors.
  • There is improved support for using QuickBooks with multiple monitors. I’m not sure WHAT that improvement is, but there must be something?
  • Save buttons can now be seen on the Write Checks window when viewing Paychecks and Payroll Liability checks in 1024X768 resolution.
  • QuickBooks Enterprise V13 trial users running R6 will not get Advanced Inventory, QuickBooks Email and the Accountants Copy File Transfer features enabled by default.

Updates/Patches

If you are reading this then you probably understand that Intuit has major “Releases” periodically, to fix problems and add new features. We are talking about the R6 release here, for example. Each release is given a “release number”, starting with R1 each year. These releases take a lot of work to build and test, before they are rolled out.

On occasion I believe that Intuit will roll out an update to customers that is NOT a part of this “major release” sequence. I’ve wondered about these “off cycle” updates, and I’ve had concerns about them mainly because there hasn’t been a way to detect when they are rolled out, as far as I can tell. See my article on an unexpected update a couple of years ago as an example.

Starting with the 2013 R6  release (in the US versions only, at least at this time) there is a new feature in the update mechanism that provides Intuit with the ability to release a targeted fix without waiting for the next full release. I’m still nervous about these, but I think I’ll be a bit happier with the process because it looks like we will be able to see if this has happened, AND possibly have some control over it. I’ll wait to see how they use this before I can decide if it is a good thing.

To see this, select Help and then Update QuickBooks, then click Update now. Scroll to the bottom of the list that you see, and there is a line for “Critical Fixes”.

Critical Fixes

If you press F2 you get a product info window that shows (along with other info I’ve hidden), the version you are running. Here what you would typically see, showing that this is Enterprise Accountant 13.0 R6.

Product Info without patch

If Intuit uses the new critical fixes mechanism to push out an update (perhaps to fix a significant flaw that has been uncovered that can’t wait for a major release) you may see something in addition, like the following.

Product information with patch

This at least gives us the ability to see that this kind of patch has been applied, which I think is critical to ProAdvisors who are supporting clients. We need to know what revision of the software a client is using when we are trying to diagnose problems.

That Is A Lot Of Fixes

Hey, it is the end of March, 6 months after the initial release of QuickBooks 2013. On one hand, I’m really glad that Intuit has fixed all of these problems. On the other hand, I find it distressing that there were this many significant problems at this point that NEEDED fixing.

Each Fall when the new year of QuickBooks is released I always tell people to wait until at least the next January before upgrading, if they have that option. Intuit’s first releases always have issues to shake out, which is partly due to the way I think they manage product updates (at least, from what I see from the outside looking in). Here it is – March – and I am hoping that THIS is the release we can have some confidence in. That is a long wait. And we won’t really know if this is the release that solves all the major ills until we see how it plays in the real world.

I must admit at this time that in my own test installations, since about the R4 release, I’ve not run into any major problems. Sure, there were some issues (like PDF’s, scanning on Windows 8) but for basic use of the software I haven’t seen any of the random crashes that other people report. I know of a number of installations where people are very happy with QuickBooks 2013. These crashing problems aren’t universal, which made it tough to pin down.

For my own business, I’m still running on QuickBooks 2012, and I’m going to wait at least another week or so before I move THAT company file up to QuickBooks 2013…

About the author

Charlie Russell

Charlie Russell has been involved with the small business software industry since the mid 70's, and remembers releasing his first commercial accounting software product when you had an 8-bit microcomputer with one 8 inch floppy disk drive. He has a special interest in inventory and manufacturing software for small businesses. Charlie is a Certified Advanced QuickBooks ProAdvisor with additional certifications for QuickBooks Online and QuickBooks Enterprise, as well as being a Xero Certified Partner. Charlie started blogging about QuickBooks in 2008 (Practical QuickBooks) and has been writing for the Accountex Report (formerly the Sleeter Report) since 2011. He retired from accounting and QuickBooks activities in early 2018.

Visit his CCRSoftware web site for information about his QuickBooks add-on products. He is also the author of the California Wildflower Hikes blog.

62 Comments

  • Charlie – you have ‘outdone’ yourself on this one. A great write-up of a mass of complexities ranging from QB ‘reversal’ of their position on moving the QB Interface to the “Dark Side” by allowing for the return of the ‘loudly screamed for’ Color schemes all the way to the very long list of technical fixes and platform/database stability changes (including links to all the right KBAs).

    I don’t think I could have done a better job on this myself. Thanks for always staying on-top of (if not ahead of) everything QB.

    Murph

    • Thanks, Murph. This release was a lot of work for me to write up, there were so many changes! I just wish I could explain some of Intuit’s notes better – I wonder what exactly they mean by ” improved support for using QuickBooks with multiple monitors”?

      • Charlie, I’ll let you know what improvements I see with the multiple monitors. Previously I couldn’t size columns on reports or double click to open a transaction or to get a detailed report if my QB file was on my fourth monitor. It was a real pain! But this was in QB 2012, I never moved to QB 2013 becuase of all the other bugs. I’ll test it out an let you know!
        I am SO HAPPY that we get our colors back!!!!!
        -Mary Longacre

      • Charlie, the issue fixed for multiple monitors was the following:

        The QB 2013 window could not be dragged or maximize/stretched to occupy the entire screen when using multiple displays with different resolutions.

        This was mentioned/confirmed later in this thread by Lance.

        Eric Raines
        Intuit, Customer Relations – Supportability

  • Nice summary. Just a nitty question from a guy who studies user interface — still trying to get it just right. Is it really easier for a reader to instantly grasp a word written in all caps? I’ve always believed that lower case words and initial cap words are more quickly recognized because of their non-rectangular shapes. Your article mentions INVOICE preferred over Invoice and DATE over Date and SHIP TO over Ship to. Seems backwards to me — what do the true UI gurus think?

    • Ken, you would have to ask a “true UI guru”.

      In this particular case, given the light-weight and small font, I do believe that having these in caps is better than what they had before. But it also isn’t the only way they could have made these more readable.

      Also, note that Microsoft has moved to all caps for certain features in their newest release of Microsoft Office…

      • I agree with Ken, mixed case is usually easier to read at a glance. However, the headings/data field names in light gray microscopic print, floating in oceans of white space and color bars that are barely distinguishable from the white space, were almost unreadable.

        Since ALL CAPS is BIGGER than Mixed Case, it’s easier to read in that respect, so I guess it’s an improvement.

        And by the way, whose bright idea was it to use tiny light gray print on dark gray title bars, again, barely readable. Don’t they test these things with real users, like seniors with vision issues, who are a goodly proportion of the population?

        Thank heaven for the return of the color schemes, that should be of some help also.

        I am forced to deal with the UI for my clients who have upgraded, but, I won’t be upgrading my own data file anytime soon, until forced to.

        And, last but not least, thank you to Charlie for yet another fabulous in depth analytical article.

    • I customise my forms – so I change things like that. My problem is in the UK we have invoices due on statement. Quickbooks has no understanding of this so all our customers and suppliers are on 30 days and we print statements at the end of the month but it makes it awkward. They need an end of month feature for due dates (30 days end of month to be specific. I tried forcing it but its not working well.

  • Nice article. I’m extremely happy with the new release.

    ” ” improved support for using QuickBooks with multiple monitors”?

    This may have to do with the sizing problem. For me, QB 2013 would never fill more than about 70% of my working monitor’s space. The bottom of the window just disappeared past the bottom of the monitor along with the Save and Close buttons and anything else at the bottom of the transaction window. No scroll bar to access it. Just manually re-sizing the window each and everytime a transaction window was opened.

    I avoided using QB 2013 all I could.

    It does not have that problem now. QuickBooks fills the screen, windows open properly. It’s usable. Glad they got that fixed!

  • Another outstanding post Charlie.
    I’d been tracking the “QBSDK applications will now be allowed to run in “unattended mode” without receiving script errors.” issue in various forums and your post was the first I saw with an update.

  • I just opened up my 2013 Premier Accountant’s version and the first thing that popped up was an announcement that R6 was available to install so I think Intuit has decided to push the update immediately. Nice not to have to download it manually.

    • Keith, in general, I’m happier when they have a week between manual and automatic update, so that we can see if there are any problems with the new release before it gets pushed out to everyone. But, considering the number and severity of the problems that this release fixes, I’m not surprised that they pushed it out right away.

  • Charlie, wow, what an article! You really went above and beyond to pull all this together. Thank you.

    So there is a fix having to do with setting up new users. That’s good; database corruption related to users is probably the biggest problem we’ve seen in 2013 files from clients.

    Another “multiple monitors” thing: I’ve noticed that QB consistently puts up its dialog boxes on a different monitor than where my main QB window is. Kind of annoying. It would be nice if the fix would make the dialogs anchor by default to the same window where QB is actually displayed, on whatever monitor that is. I’ll try it with the update and see if there’s a change in that.

  • Charlie,
    Another great article. Not sure how you offer so much more insight than the R6 release notes, but I am certainly greatful that you can and do just that.
    Maybe you should talk Intuit into just using your blog as the release notes…

  • Totally different topic (I couldn’t find your email address…): Is there a checklist available to help produce a better conversion for clients going from Quicken for Mac to QuickBooks for Mac? Right now we have to go through Quicken for Windows and QB for Windows, and Windows just doesn’t like & or / in any names. And the conversion doesn’t handle sub-accounts deeper than the second level. It is possible to do if you have a copy of each program of the same darn year, but the results pretty much suck (thousand of transactions without corresponding account names). Any help in this would be greatly appreciated!

  • Thanks for the timely info as always, Charlie! Was hoping you could shed some light on a long-time QB feature that has not worked for me since we upgraded to Enterprise 2013. That is the ability to find Customers/Jobs in the Customer list by typing the first few letters of the name. For instance, I used to be able to type S-L-E to find a company named Sleeter Group (or at least get close to it.) Now when I type S-L-E, QB jumps to the first “S” customer, then the first “L” customer and finally to the first “E” customer. Since I have a very large customer/job list (we do a lot of service work), this is very frustrating. I’ve searched online for instances of others experiencing this problem but really haven’t seen anything about it. Do you have any insight to share? Any help vastly appreciated.

      • We were forced by the Real Time Initiative (RTI)compliance to upgrade to Quickbooks Enterprise Solutions 13 Vr 6. The upgrade has been extremely problematic and left us using Enterprise solutions in single user mode for payroll and revert to Quickbooks Premier 2012 to run the rest of the business. This situation is untenable in the long term and Intuit seem unable to address our problems despite considerable effort. We have been a loyal advocate of QB’s over 15 years of trouble free offering. We could not recommend the upgrade to QBES!

  • Hi Charlie,

    Do you know if batch entry will include items soon? That is the one thing that I could use the most for 3PL. Most of the suppliers bills are direct conversions to invoice at markup. I don’t want to build templates for only 10 deliveries a week but the keying is rather tedious when they come in on a single day. Any great ideas to streamline?

    Thank you!

    • Julia, anyone who knows the answer to that is bound by a non-disclosure agreement until the product is actually released, unfortunately.

      Depending on how your info is coming in, you might find that you can use Transaction Pro Importer to convert and automate, but I can’t say for sure without seeing your source data.

      • I recently started to use the Transaction Pro Importer and it seems to be working fantastic. However, each time I use the software my data file increases in size drastically. 4 x drastiacally. 700 mb to 3000 mb. Luckily, I am not using my live data. Have you seen this before?

        • Without knowing what you are importing, there isn’t any way to comment in detail about this. Either you are importing a lot of data, or you are doing something that involves a feature like multiple locations or serial numbers (something in Enterprise with Advanced Inventory), where some kinds of operations that you can do (through the keyboard, or an import tool, or anything) can cause the database to enlarge quite a bit. That situation isn’t TPI, it is Enterprise itself.

          You should talk to the folks at Baystate Consulting through their support forum about this in more detail.

  • I am running QB 2013 Enterprise Solutions Manufacturing & Wholesale…I am wondering if there is a way to run a cash requirements report based upon the vendor bills that you plan to pay? Currently, under pay bills you can check off each invoice you want to pay but from there it’s either print those checks or come back and start the process over. I’d like to run a report based on those that I’d like to pay in order to get approval to do so. Any insite would be appreciated. Thanks.

    • Shaun, you can go through the Pay Bills process and check off all of the bills you want to pay, and mark them “To Be Printed” but when you get to the screen where you are given the option to print the checks, just click “Done” instead. Then print a check register for the Check Date and present that for approval. (It will show the bank balance too, assuming your entries are up to date.) You can print an Unpaid Bills report (run after the bills are paid) so that you can also show the bills you haven’t paid.

      If there are any checks that you don’t receive authorization to print, just delete them from the register and the bill will go back to being unpaid. Then you can print the checks that have been authorized.

      -Mary Longacre

    • Brett, there should be no relationship at all. Assuming the date is the same as the one I show above, it doesn’t represent anything that made any change in the database (going from plain R6P to what you are seeing).

  • Hello We have had a horrible experienced with the Enterprise Solutions V13 update. We have used the product for the last 15 years and always waiting until the last minute to update as we have always had probs. Thought we had waited long enough this time but just last week we updated and had incorrect data processing in our YTD columns in our first payroll. Tech support after many hours on the phone was unable to correct the “bug” as they call it…Our data file had to be uploaded and we first dealt with support in the Philippines, and now we are dealing with Tech support in India. Our data file is still out there and no one can tell us when we are going to have it back or whether it can be repaired. It will be a week tomorrow. I have called all the way to the President’s office of Intuit and each time I get shifted back to the Philippines or India….I have this morning called back to the original sales rep who assured me we could now get US support when we purchased the upgrade…Again shifted back to the Philippines…This is very costly to our company not to mention the security issues we feel exists as we are a medical care company and have uploaded a large data file with not only patient info but employee data as well. This problems, we now know, was “blogged” about on Intuits own community board back in Feb 2013 prior to our purchase. So their programmers I am sure were aware of this problem. NO ONE contacted us and said, DO NOT UPGRADE until we fix these issues..Do you know if we have any legal recourse when a company (Intuit) knowingly sells a product with defects and causes damages to the buyer..in our case our data file of 15 years…Please post this so others will not have to experience what we have and perhaps someone will consider this as a CLASS ACTION case against Intuit. We will gladly join as I have kept extensive notes this time with everyone with whom we have spoken…Thank you and I look forward to an opinion from you. Karen

    • I agree with you Karen, we have a client with a very similar experience. There should be a class action case against Intuit. Not because of the bugs in the release, but because of the hidden truth and run around. This has exposed Intuit as a company that you can’t trust.

  • When I try to send reports(specifically inventory by valuation summary) to excel, quickbooks crash or abort. This happened since I updated to R6. Please help me because my boss wanted to kill me because of this. Thank you.

  • hi Charlie. I cannot search customer by pressing enter in QB Enterprise 13 R6, I need to use my mouse to click the search button (very frustrating simple thing!). But in QB 12 I can. Please fix this.

    • Well, I can’t “fix” anything, as Intuit is the developer of QuickBooks, not me. At what place are you saying you were searching for a customer? In an invoice, or what?

      • In Customer Center. After typing the word you want to find usually you hit enter and then it’ll come. But now after R6, nothing happens.

        • Mon, I don’t see it working any different in R6 than it did in R5. I didn’t go back further.

          If you are using the search box in the left side of the customer center, you can type a value and then hit the tab key, then the enter key. Tab will take you to the “search” icon at the right, enter then makes it search. So that is two keystrokes, not one.

          If you enable your preference to “enter goes to next field”, then you hit enter twice to get the same result.

          That works in R5, R6, and the current release, which is R8 at this moment. I didn’t go out to older revisions.

  • I wonder if anyone has noticed you can no longer ‘save’ your notes on items after R6. Regardless of premissions and I am on R7P now! Oddly – the way round it is to state OK after entering something on the item notes then click on cancel on the next page. If you press ok it doesn’t record!!

    I wasted 2 hours with that one and my Warehouse manager is fumeing as it’s weeks of work not recorded!

      • I’m in QB Premier 2013 R7. I just tested some of my item notes. It seems to only be a problem with inventory items. All others seem fine. What are these notes generally used for?

        • Personally, I find them of limited value, since you can’t use them in many reports or screens (and most if not all add-on products can’t easily get them). You can store internal notes there, for your own reference.

  • R-7 in a 3 user networked environment is a disaster. Since 6/13 download of the “upgrade” any attempts to work in a networked environment result in repeated frequent spontaneous shut downs. And I can’t download inventory assembly files to an Access Data base without fatal error and shut down. Attempts to use back ups from R-6 resulted in a data conversion to R-7 file structure so even old files can’t download to Access.

  • Every day this week I have shut down Quickbooks in multi-user mode and it opens in single-user mode. My boss, who gets to the office first, says he’s been getting an error message that he can’t log in since I’m in single-user. We are both on the same release and it doesn’t look like we’ve had a new one since late June but this just started happening this week. Any thoughts?

    • Kim, hard to say without knowing more about your setup. Where does the database reside? Is it on a server, and is the QB database manager running there, or is the database on your system locally?

      • We only have 2 machines- no server. I think it’s on my computer as it has to be on for the boss’s Quickbooks to work. The problem didn’t happen this week although I did get the message this morning that QB needed to open in multi-user mode, etc. I didn’t even go into single user yesterday. I know that little glitches that are easily ignored or worked around can be a symptom of a larger problem so I don’t like to ignore them 🙂

        • Kim, lots of time the issue pops up when your boss turns his system on and your’s isn’t available – it then wants to try to be the “server” for the system. In multiple user mode there is a “database server” program that is running, handling all of the requests for access to the data. This should always be running on the system where the data actually exists. But, sometimes, you can get some conflicts when two different systems think that they are to be the server.

          The details of this are hard to work out via comments in blog articles like this – the best way to address it is to find an accounting professional who is very familiar with this aspect of QuickBooks so that they can look at your system to see what is going on. You may try clicking on the “find a consultant” graphic at the top of this page and find someone who is close by to you.

Leave a Comment