@Richard Cooley Thanks for posting. Actually I like your suggestion for maintaining communication among users so that all may see benefits or pitfalls found by others as they search for suitable substitution software.
While I’d be glad to be one of those sharing info, it may be a bit too early. School is not out. TT has yet to respond to this debacle. Regardless of the adequacy of their response, we’ll learn something either way, good or bad. I’ll be patient to see what they do, and remember that the grass always looks greener on the other side of the fence.
There’s no sense in sugar coating incompetence when it occurs and the sponsor of that error compounds it by stonewalling with a total lack of communication. Exposing that becomes part of good analysis as we all try to determine what alternatives improve our lot. By the way, I still have not had even a boilerplate automatic email telling me (as promised) that the problem has been fixed.
Here’s hoping we can all continue to communicate. My best to you,
John
