opening fasterassembly always modified

[uwam2ie]

I have added a fastener assembly stack in NX7. I've used the hex nut 1A, Din,M10x1,5 in the stack configuration.After save / close and reopen the main assy the nut partfamily child always open modified. What went wrong??
thx in ad

 

[looslib]

Was the part fasmily and fastener assembly resaved in NX7?
Any components in an assembly from an older version of NX will cause the modified flag.

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

Ben Loosli

 

[uwam2ie]

thx Ben on reply,
I checked it the Nut was saved in Nx7. The problem seems to display, when the load options are not working for the partfamilies on first open the assembly.
As saved is working fine. Load the partfamily loading in second step with modified load options is causing the problem.
But why, thx

 

[phillpd]

Is the "Generate Missing Part Familiy Members" (Load Options) coming into play and causing the issue ?

Specialty Engineered Automation (SEA)

http://www.sea4ug.com

a UGS Foundation Partner

 

[uwam2ie]

thx phillpd on your reply,
I have checked the load options on generate Missing...
but this has no influence - as I tested.
The question still is why get the (only the nut)partfamily child get a modified flag on reopen - The partfamilies are all from the siemens ootb machinery libary but doesn't work.
thx

 

[hudson888]

Somewhere along the line I sneakingly suspect that you may not have write access to some of the files. Members of part families do often warn users seeing to make changes on the fly to their member files that they're read only and this is done in order to ensure that control of the output derives from the spreadsheet. While you're not specifically reporting this in your posts it seems possible you may have overlooked some kind of write access problem indirectly without being aware of it.

The only other thing I can think of is that two files of the same name have been created in different directories with the system deferring to either your load options setting or the part family directory as set in your defaults given the the fastener in question ostensibly remains a part family file. I can't say I've seen the latter so I'm not entirely sure what happens if you do the inadvisable by naming another fastener file exactly the same as a part family member. Clearly changing the name of the file in the assembly would be both my first recommendation and a great way to test whether something of this nature might solve your dilemma.

Presuming that you're running in native throughout my reply I would add that for rooting out duplicate filenames in different folders or directories using windows based file systems an effective utility called doublekiller can be downloaded as freeware.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[uwam2ie]

-- I've just installed the MR 7.01 the problem seem to be fixed. I'm still testing but I think its fixed.
thx to all give me some advice