@Gail Badner This bug doesn't exist on version 5.2.12, could you please back port those changes to 5.2.8?