it's fixed! Thanks for the quick response on this issue.