I did get an answer from Tech Support. They are aware of this problem and cant correct it now. Said would just have to live with it. Will try to correct in next vs. Hopefully the new version 1.4 will have it corrected.

Thanks for everyone's answer
Tom