Although I would prefer MACRO commands I am open to use Visual Basic, or GRIP or another way.
I am completely new to GRIP so I would need to learn the syntax though.
Currently from the CMD Line this is run
ugraf.exe -key=t:\m1.macro
This macro Opens NX sets windows sizes & toolbars & closes NX (so macros will work correctly).
Ugraf.exe –key=t:\m2.macro
This macro opens part.prt, updates expressions from an external spreadsheet, saves the part.prt & closes NX. I run this multiple times.
The bottom line is it takes longer than necessary to open & close NX if I run m2.macro multiple times. Can it be updated without closing and reopening NX?
I imagine this running (or something comparable to it)
m1.macro or VB Code (This macro runs, Opens NX updates windows size & updates parts & stops & leave NX OPEN)
Then Later I will need to run (multiple times)
m2.macro or VB Code (This macro runs, updates the expressions from an external spreadsheet & leaves NX OPEN)
If I try to call a macro with NX open from the CMD Line NX does not like it to say the least.
Alanhiggy
I am completely new to GRIP so I would need to learn the syntax though.
Currently from the CMD Line this is run
ugraf.exe -key=t:\m1.macro
This macro Opens NX sets windows sizes & toolbars & closes NX (so macros will work correctly).
Ugraf.exe –key=t:\m2.macro
This macro opens part.prt, updates expressions from an external spreadsheet, saves the part.prt & closes NX. I run this multiple times.
The bottom line is it takes longer than necessary to open & close NX if I run m2.macro multiple times. Can it be updated without closing and reopening NX?
I imagine this running (or something comparable to it)
m1.macro or VB Code (This macro runs, Opens NX updates windows size & updates parts & stops & leave NX OPEN)
Then Later I will need to run (multiple times)
m2.macro or VB Code (This macro runs, updates the expressions from an external spreadsheet & leaves NX OPEN)
If I try to call a macro with NX open from the CMD Line NX does not like it to say the least.
Alanhiggy
