opening a part modified

Assemblies can be modified for different reasons than parts because their structure is changed or potentially changed any time you open them with any other load option method except for As Saved. Another confusing source of things being modified even if you haven't apparently changed anything is changing from older to newer versions of NX. If any parts you open haven't been refiled then the system always reflects that they need to be saved in the newer version.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

- ok you right hudson. there are a lot of reason why. Simply I want to have (sometimes) information what causes the modified status. Now it is a guessing game , look here do this try this save - test - ??? No strait way - or can somebody give me advice in general what to do? thx in ad

There's NO practical way to do this in a manner which would be both accurate and comprehensive, and without being sure that what you're being told is at least 99% factual, what good would it be anyway. As Hudson mentioned, the number of variables and factors can be significant. In fact, there has been serious debate about eliminating some of the more esoteric checks (or at least reporting that they indicated a change) simple because many of these things are stuff that even if you knew the details, it would be of no value to you whatsoever.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

To an Engineer, the glass is twice as big as it needs to be.

thx John on reply, for you it:
the glass is twice as big as it needs to be.
But it is unsatisfing to search/guess for the reason,why.

The reasons an assembly is flagged as modified are just too many to even worry about. I have opened a file, saved it, closed and reopened it and it is marked as modified.

This is one of those things that in the scheme of life, it is best to just let it ride. Clean-up your componeents as best you can and move on.

Modified reasons I can think of.
file (assembly and/or component) at older rev of NX
mating condition fails
reference set name changed
using zone filters
interpart dependencies
It's April 1st and the system wants to play with your mind




"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli