As I've just posted, it seems to stem from upgrading to version 2.0.5 earlier today. I think someone else suffered the same problem earlier in the year. Alas I don't know how to correct the problem. I'm just hoping that no more are marked as new! Mike -- Mike Little http://zed1.com/