Actually I have errors executing .DLX files. I am testing them on Windows 8.1 and NX9.0.2.
They run on NX8.5 and Windows 8.1
On a custom drive, D:\1000_DEMO_NX9\000_NX9_CUSTOM\NX90custom\NX90lib
When I run the .VB file located on ...\UGALLIANCE\site\application the .DLX file not found.
Solved! Go to Solution.
The location of the application folder containing the .dlx file needs to be defined in a user directory specification (UGII_USER_DIR / UGII_GROUP_DIR / UGII_SITE_DIR or UGII_CUSTOM_DIRECTORY_FILE). In this case, the path:
should be defined in one of these locations. Check the syslog to ensure that these are defined correctly in the NX session.
You are right.
One question, which is the diference between UGALLIANCE_DIR and other variables?
For pointing .VB, DLL and .DLX files?
There's also UGII_VENDOR_DIR.
Functionally they are all equivalent.
VENDOR and ALLIANCE I would reserve for Siemens' partners to use, I would use SITE (or maybe GROUP) to share with other users, USER if I only wnat to see it myself.
Unless you want to use UGII_CUSTOM_DIRECTORY_FILE
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX11.0 EAP, NX12.0 EAP
How to Get the Most from Your Signature in the Community