Hi Per,

It was the same error message as Wil was referring to, but it works now with the update you provided. Thanks.