On 06/08/15 15:38, Pat Riehecky wrote: > The problem should now be corrected. Yep, it all seems to be working OK now. Thanks for the lightning-fast response. Regards, -- Colin