assembly - accidentally modified components

[aligil]

Hi gurus,
I have a tarlo that persecutes me: working together for assemblies, I often find components (or even subaxis) that are modified though they have set them in read-only.
the terrible thing is that they seem modifications caused by the product such that, even if I close everything and reopen the product turns out to regenerate and I recapture the modified component, to note that I never made it feature of together !!!

in pro/engineer is there a possibility to update the component and cancel its changes (maybe simply reloading the unmodified component), in caia there is a way to update inside the axieme a component to cancel the accidental changes?

I apologize if I've stretched but it's something that's driving me crazy because then the modified components cause me updates in all the other assemblies with the relevant food... .

 

[gianni55]

working together for assemblies, I often find components (or even subaxis) that are modified though they have set them in read-only.

1) if the catproduct file has the modified attributes (from the property of the windows window) in read-only, when you open it with catia appears (for force) the message "advertence the xxxx file is read-only", and you can't change it (except you change the name)

2) if the catpart files contained in the product (read only) are read/write, they can be edited even if contained in the blocked product

3) if even the catpart files contained in the product are read-only, when you open them with catia appears (for force) the message "advertence the xxxx file is read-only" cannot be changed (except for the name changes)

questions:

4) Does the message appear to you at the opening?

5) the same message appears to you in rescue management?

the terrible thing is that they seem modifications caused by the product such that, even if I close everything and reopen the product turns out to regenerate and I recapture the modified component, to note that I never made it feature of together !!!

6) the changes "look" caused by the product, but are they actually occurred? have you noticed something different than your initial design?

7) sometimes even only the opening of a catpart and a trivial operation as re-enter into a sketch and exit without any modification, a modification is considered by the system.

8) the rescue management is the best method to manage the changes actually necessary and desired by the designer

the modified components cause me updates in all the other assemblies with the relative puts at the table

9) if they were really read-only, they cannot have changed, if they were read-writing, it is possible that some file opening operation, sketch, copying etc. led the system to consider them modified you saved them automatically, so they are recognized as varied and need update. If you don't create too much trouble and have doubts, you could block the view to avoid updating.

in pro/engineer is there a possibility to update the component and cancel its changes (maybe simply reloading the unmodified component), in caia there is a way to update inside the axieme a component to cancel the accidental changes?

10) in caia in the rescue management you can restore the previous file only during the rescue operation, but when you closed the window nothing is as possible

11) in caia you can accidentally replace the catpart with the original one by overwriting it inside the folder to which the product points, but it is an operation to be done with caution and knowing well what you are doing, perhaps by making security backups: the trouble is that if you do not master the modes of rescue, it is a moment to make trouble

to avoid these problems, it would be better to adopt some sort of tricks:

save validated files, in specific read-only areas for everyone.
possibility to save in those areas only by the head office or seniors
each user works locally and passes to the manager the finished job to store

Let me know.

Hi.

years ago

 

[aligil]

Gianni, I apologize for my crazy delay but I was pretty
messed up with work.

my answers point by point:
1, 2, and 3 - I am aware of what you write
4 and 5 - changes result in rescue management but only after
regenerated the product, if not regenero seems all normal, for this
I have the feeling that the changes are "caused" by the product.
in pro/engineer (on which I have seen of cooked and raw) it is possible
create terrible loops together, but I don't think that's the case.
because it's sub-product that I just assembled.
6 - I say that "they look" caused by the product because if I open only the
sub-product is not detected any need for update, just apro
the product that contains it is reported to me the need to update
and consequently (in rescue management) the sub-product is
modified.
7 - for personal "culture" I never go into a sketch to see it
size (there are the appropriate tools to measure. . . ).
8 - correct, but it does not solve my problem as to regeneration
next the whole thing resurfaces.
9 - the problem is that read-only defends from rescue and not from
change.
10 - "...in rescue management you can restore the previous file. . "
in reality you can only avoid saving but the object remains modified
and to be saved (according to cat)
11 - san pro/engineer when saving makes a new version (files have
double extension type file.prt.125 for which it is easy to recover a
previous rescue.

last: management tips are definitely useful but remains the pigeon
of involuntary changes during the development of the project.

thanks anyway for the interest

alessandro

 

[gianni55]

4 and 5 if a product caused undesirable changes to a sub product, I think there would be many people with holes under the dassault offices. .

6 more easily from the product you will have performed an operation (voluntary? Involuntary?) on the sub product that the product recognizes but fails to save due to the licenses denied (in the sub product). in turn the sub product opened alone contains no modification (which are in product memory) so it does not generate any request for update

8 is worth explanation of point 6

9 For if you have modified it (voluntarily or unintentionally) and then do not save it, the system continues to insist that the inconsistencies are resolved.

10 now without analyzing product and sub product it becomes difficult to understand what happened and how to remedy it. . I would try (by making a copy) to open the product, delete the sub product, save the product, close the catia open the product again enter the sub product (without touching it in any way), save, close and reopen and check if the update request remains.

this if the problem is only the sub product, if instead it is a part that is not updated (or that has an error that prevents the update) you have to look for in the sub product.

Let me know.

 

[falonef]

Have you tried to clean the files with the catdua?