On 24/07/2012 07:42, Chris Travers
wrote:
I've just tried it again and I can't reproduce either, although it was a solid bug when I reported it. Now running 1.3.20 and I can only assume that some other change has had the side effect of fixing it... sorry for the trouble All the best Nigel |