@ Al
I was finally able to replicate this error in my testing enviroment. I was able to track down and correct the error. The next update will contain the fix. Apologies for the trouble!
