Rea_M, I've stayed quiet for several replies to this thread, but after your response, I must interject. I posted this problem and I was a ProAdvisor for about 5 years. I am flabbergasted, that you dare to think that all the people that have chimed in and stated they have experienced the same issue, do you really believe none of us have contacted the "Customer Care team"? Please do not take offense, but I have ZERO faith in the front line group to handle a problem such as this. I have submitted "feedback" when I receive the crash window(s). I have requested call backs, escalations, you name and with no assistance. I'm told it's a "known issue" and they are working on the problem. This has been occurring for a couple of versions of QBDT, not just 2019. I find it very demeaning that you "pop-in" and politely tell us how to solve the problem in your utopian world. We businesses pay good money for this program and now TONS OF money for this program due to the new subscription model, and that's the best Intuit QuickBooks has to offer me/us? Nice try, but shame on you. What happened to fixing something rather than slathering on niceties and expecting that to cover many software errors that remain unsolved. So, unless you have something to back it up, please share your pleasantries somewhere else.

BTW - I have upgraded to 2022 Pro Plus, we've paid over 800% more to be "entitled" to use this program for a year to include all the tech support we need. But, what's the point when problems, very similar to this, are merely swept under the rug and NEVER fixed! If our company was so entrenched in this product, we would be seeking solace in some other accounting program. Not to mention, we are small businesses which don't have the luxury of being on tech support calls for 2, 3, and 4 hours, only to learn the problem is escalated - into the ether?! That's a cost that you nor Intuit can replace!

I was going to apologize for my curtness, but your post really incited me to take time out and shed some truth on the matter at hand! Anyone at QBDT that cares to repair this issue? I've not seen it for the 6 years I've experienced this issue. So, I doubt that the impotent first line of engagement, known as the Customer Support Team, will be able to solve this SNAFU.

Ciao for now,

Jbear1212