Another matter... Why not use this.Save() rather than this.Save(entity)? Looking at the WW source code for the Save() method shows that any time you pass in a entity, it creates a new context, and then attempts to InsertOnSubmit() for new records, or Attach() for existing records then it calls SubmitChanges().
Why not just do a plain old Save()?
That's just a mistype in my post. The second UpdateStatus accepts the entity parameter. In my case I wanted to support both scenarios - saving current entity or the passed in one. But I just removed entity from the Save() as a test and it appears to work. No idea why there would be a difference by doing that, though. Not really in the mood to trace through the code tonight, maybe next week. Thanks.
-Paul
