Sorry for the delayed response. I haven't been checking here recently. It sounds like the problem may have been due to a bug that was fixed in build 119. If that's not the case, please let me know.