- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
This was fixed on the August 5th QB update but started again September 20th.
I have contacted technical support and was told to contact Microsoft and they denied ever having a fix for this issue.
I am terribly disappointed that they are telling end users to contact Microsoft for a problem that is affecting hundreds of users. It should be their responsibility to have this working correctly.
Please get this fixed as it is a terrible inconvenience in how we communicate with our customers!!