@jdaviescoates thank you for your answer. It seems after further inquiries that it was due to a cache problem. I went over it again and all went well.
J
jimmmmy
@jimmmmy
@jdaviescoates thank you for your answer. It seems after further inquiries that it was due to a cache problem. I went over it again and all went well.
@brutalbirdie yes, thanks 