WinAutomation Logo

I'm not sure which forum this belongs to but my question revolves around the parent-child nature of the jobs.

The crux of the issue is the external variables. They seem to be available for the child job BUT if I compile both the parent and the child, then I can't use the external variable? That would kind of make sense since these are now two separate EXEs with their own memory management.

If I go the other way, and do the Run Job action and then compile both the of them, it doesn't appear that the child job is run at all.

 

Any advice is appreciated! Thank you.

I may have figured this out myself...

If I use command line parameters, and play with that, all seems well between exes.. I have to use an executable.. can't use run job in the production. And that is interesting because it would be nice to be able to switch from Run Job to Run Exe seamlessly between test and production. I'm sure I could use a DB or a flat file to accomplish the same but command line args are elegant... oh well. Looks like I'll be using exe.s for both test and production.

Hi Kim and everyone else who is interested it this one here, I am attaching a job file that will help you understand how you can have both, it does require having a few extra actions within the job, but does help you in the long run. :) Samantha