That's validating - at least I'm not alone :)
Charles
"Dave Matthews" <dav### [at] mnwestedu> wrote:
> I've encountered the same problem in the same situation, and my solution was> to go back to version 3.5, which doesn't have this bug (which is fine, as> long as you're not using any 3.6 features.)>> Dave Matthews