I don’t feel the need to comment on this further at this time. You all have recognized the problem and we’ve been told that the target date to fix it is Feb. 2016. I appreciate the support we get on the previous version knowing full well that no new development will be performed on V10. I’m thankful that most of the issues our users experience are known and we can employ known good workarounds in these instances.
Share this Post