And I can see you are replying just fine. I cranked up the debug so when you have the opportunity to try again hopefully I can capture the error. Suspect this is probably a bug somewhere that you've uncovered.