@Gail - since this issue is unresolved for version 4.1.6, even if I upgraded to the latest version I am assuming I would still see the same issue? Or are you telling me it is resolved in later versions after 4.1.6?