Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Journal or Macro to run .EXE files

Status
Not open for further replies.

Kenja824

Automotive
Nov 5, 2014
949
We have an .EXE file that we would like to create a button to automatically run. When I recorded a Macro to run it, it only partially worked. We would hit the button and the macro would run like it is supposed to. But at one point when the exe file goes into a second part where the user is supposed to select something, the exe file stops working correctly. It will allow you to select what you need to select in its options but its as if its buttons stop controlling anything. .... HOWEVER ..... If we hit CTRL-U and run the EXE file without the macro. it works perfect.

I have come to the conclusion at this point that what happens is the exe file starts running and the macro is still recording until you are finished. So the macro is running and the exe is running and cancelling each other out some how. I think what we need is a macro or a journal that will allow us to run the exe file, but will stop running as soon as the exe file has started.

I tried to record a Journal but cannot find in the journal where it opens or runs the exe file. Instead it looks as if it records everything the exe file does instead.

Is there a simple macro or Journal that just runs an exe file, that I could just go into it and replace the path and file with the one I want it to run here?
 
Replies continue below

Recommended for you

With .net, you usually compile to .exe for "batch" type processing (no NX session running) and you compile to .dll for programs that will be run in interactive NX (this very general rule may not hold for non-.net languages). I suspect the exe file is launching its own, separate NX process to work with and doesn't know about the interactive session you have running. The "execute NXOpen program" command somehow tells the exe to use the existing NX session; the journal to launch the exe does not.

www.nxjournaling.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor