Component Name vs File Name

[magnum164]

ok, not sure what happened to my first post so will post again. I have been tracking down a source of crashes in NX5 related to other software we use. What I have found is we get converted files from a UNIX machine and we end up with filenames and component names not being the same, as far as upper/lower case. Our systems are case sensitive so the following would be different parts:

File Name: MyPart.prt Component Name: MYPART.PRT


I need to know if this situation can be captured in Checkmate or something where we can prevent the users from going further until corrected?

 

[JohnRBaker]

Note that there is an option which you may wish to try. In the ugii_env.dat file there is a variable which can be set which will force NX to convert files names to all UPPER or all LOWER case. The following is a description of the option:

# File system options. If LOWER is set, filenames will be converted to lower
# case before being used. If UPPER is set, filenames will be converted to upper
# case before being used. If neither is set, filenames will be used as the
# user types them in.

For format for the variable is:

UGII_OPTION=LOWER

or

UGII_OPTION=UPPER

Anyway, try changing that in you ugii_env.dat file or adding this variable to your user/system profile.


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

http://www.siemens.com/plm

http://www.plmworld.org/museum/

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

 

[magnum164]

We originally had that option set but a test machine when setting that option it prevented out integration from starting. Not sure why, but the menu's would not activate. There is a sever configuration option on our PDM that forces object name on checkin to caps, but is ignored when the UPPER is defined in UG, so I suspect there is an issue there.

But, that would only prevent users from creating files, not sure what it would do with files that are supplied as lowercase to us from other companies? I can easily test it again tomorrow.

 

[magnum164]

I did veryify this. The UPPER works if you start/build everything from scratch. However, if you switch to UPPER and you call up an ASSEMBLY taht has parts that are already named lower case and do a "Save ALL" it saves the parts as UPPER and renames on disk. However, the next time you call that assembly up, it gives an Internal error: Memory access violation on the part that it renamed.... interesting.