Thanks Marcol, this latest version seems to have fixed that error message.

Thanks too to RoyUK for your advise.