I just upgraded to 1.0.5 from 1.0.0 and the problem has disappeared. Thanks so much, Larry, for the quick and helpful response!
Cheers, Philip
I just upgraded to 1.0.5 from 1.0.0 and the problem has disappeared. Thanks so much, Larry, for the quick and helpful response!
Cheers, Philip