I've dealt with corrupted workspaces before, several times, starting back on
Ilink 3.0 & was able to recover all modified objects. It was a pain but not
impossible. Then again it these workspaces were not huge, with likely under
100 objects. As long as users follow best practice, checking in regularly,
at least before going home, I would think the danger is minimal.
Not that a corrupted Workspace is tolerable, not that it doesn't waste
valuable time, but in my opinion, it shouldn't stop a company from deploying
m060 & moving to WF4.0. I was surprised to see PTC not recommending
deployment, specially months after depolying it. Let's hope they are able
to resolve the issue soon. I agree with Eric, we really need to hear from
PTC on this.
Regards,
Joe S.