> No, I skipped 3.3.0 and upgraded directly to 3.3.1. I trust Scott > wouldn't have marked it as fixed if he didn't actually fix it though :). I'm sure I fixed it at some point but we don't have regression testing of that scenario right now so it's probably going to be a constant fight. -- Scott