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
Post a reply to this message