Component Name vs File Name
Component Name vs File Name
(OP)
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?
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?





RE: Component Name vs File Name
# 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.
RE: Component Name vs File Name
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.
RE: Component Name vs File Name