🤣 The fix: Our software works perfectly on systems that only run our software. 😂
Respectfully, that's not a solution. This used to work just fine and I've always had SQL installed on the system I ran QB on.
I did verify yesterday that this is not unique to SQL 2012 as was reported earlier in this thread. I am running 2019 and had uninstalled all traces of 2012 and the problem persists.
Please have the engineers continue to discover why an installation of SQL would conflict with this feature inside of QB and please do get it resolved once and for all. Thank you.
