Losing work from SmarTeam
Losing work from SmarTeam
I am having some troubles with SmarTeam and I hope that someone here has a solution for me. At my company we use SmarTeam with Catia v5. I will first state my confusion with some SmarTeam behaviours and the problems it has given us, and then a small description of how we have set up the models' parent / child dependencies.
The first and biggest problem is that I have been working on an assembly after checking it out, and upon completing the work, I have checked it back in. The following morning I opened that same assembly from SmarTeam (readonly, so without checking it out) and immediately saw that none of my latest work was present in those files. I checked a bunch of versions (we hadn't done a global update yet) of the assemblies and parts that I had worked on, to see if my work was saved in any of the older versions. No luck. I guess that before opening the assembly, my latest work was still present in the local work folder, but by opening the (outdated) assembly from SmarTeam, the files in the workdirectory were overwritten, getting rid of the correct versions of the files. In the local workfolder the .cgr files presenting the latest work can still be found, but they are useless for reconstructing the parts themselves.
Main question here is off course: can any of you come up with possible reasons why my latest work was not reflected by the latest (or for that matter, any of the) checked in versions in SmarTeam?
The other for me unexpected behaviour of SmarTeam is that every now and then, when I check out an assy from SmarTeam, all higher level assemblies, all the way up to the top-level assy are checked out. It must be connected to the way we have set up the parent child relationships throughout our model. Can anyone clarify this for me?
So how our models are set up is that we have a couple of "support geometry" assemblies. Basically skeleton assemblies from which we copy appropriate points, surfaces, etc, and then we "paste special" them in the newly created parts, using "paste with link".
When designing in context, we project or intersect geometrical entities directly only within parts individually. When we need to use contextual geometrical entities from other parts, we always create publications for those.
Last thing is that I seem to have more issues with these problems on my computer than my colleagues on theirs. Can it be related to some setting or configurations in SmarTeam specific to my machine or am I just doing something wrong?
Probably, this is not a lot of information to go on, so if you need any additional information to see if you can help me, please let me know.
Thanks in advance,