Skip to main content
S
setesting
July 27, 2021
Question

Direct integration

  • July 27, 2021
  • 1 reply
  • 0 views

Hi All,

Direct integration stopped working about 4 weeks ago. Since then I have spent about 16 hours online with specialists from both the QB time side and desktop side. We have attempted all of the fixes on this platform as well as a few others. I have reinstalled QB, and Windows 10 as well

   My supposition (since QB has known about this for at least 2 months) is that QB is not interested in repairing the break since the desktop functionality is not a long term concern. Online is the big guy, so the rest of us desktop users are not so important. I hope I'm wrong!! I have an awful lot invested in this system, but will have to say a tearful goodbye if this kind of careless attitude persists. The folks you talk to on the phone are very concerned, some are upset, but they are not the issue. The programmers and engineers of the system work like all the rest of us do, so have people that they need to please, so I don't blame them. I'm afraid that the blame falls squarely on the shoulders of the folks at the top.  

   I have attempted to use the direct connect method as well but consistently get the .net framework error stating that Unhandled exceptions ...... So currently I am unable to transfer any info from QB time to QB desktop. I now spend lots of extra time copying and pasting all of my employees time and comments from one to the other. (I do T&M work), I don't know what my next step will be, one thing for sure, since I'm on subscription I will not continue to pay for a non functional product!  Not sure how many others are in the same boat as I but am toying with the idea of beginning a class action lawsuit, not that I will get anything from it for myself,  but just to get their attention.

   Any advice would be appreciated.

   One very small glimmer of hope was afforded me from one of the time sheet employees that there was someone in the community that knew how to change the date and version of my first QB file (V6.OD R3 02/13/99)  So that Direct Connect would work again, sadly that person has not been located. According to that person, the first file listed in the "versions used on file" list in the "F2" window must be 2015 or later and v26 or greater. This prerequisite apparently was added a month or so ago, probably to fix some other issues.

   

1 reply

MariaSoledadG
MariaSoledadG
July 27, 2021

I wish I could make it better and will be able to make up for those times when direct connect didn't work, sutherent.

 

Generally, if you're getting a .NET Framework error, QuickBooks may not properly work and that may be the reason why there are issues with direct integration. You'll want to update QuickBooks to the latest release to install the latest updates available. To set up automatic update, follow the steps below:

  1. Go to the Help menu and select Update QuickBooks Desktop.
  2. Go to the Update Now tab. You can select the Reset Update checkbox to clear all previous update downloads.
  3. Select Get Updates to start the download.
  4. When the download finishes, restart QuickBooks.
  5. When prompted, accept the option to install the new release.

Please check this article for additional information: Update QuickBooks Desktop to the Latest Release. Also, I've included this article for your reference: Set Up Bank Accounts for Bank Feeds in QuickBooks Desktop.

 

However, if you still encounter issues with the integration, I suggest reaching out to our support team again for a follow-up. This will also be the best way for them to make the second move and prioritize for direct connect to work. 

 

Additionally, to give you a better experience and fix issues, these release notes explain what is new and improved: Release Notes for QuickBooks Desktop 2021.

 

Let me know if you still have questions about the integration. As always, I'm always right here to help.

Terms & ConditionsAccessibility statement