That's it!! No more implications for me.. next time I'll just be blunt! \:D

Excellent bluntness on your part, too, Richard! I'll be stealing the RegEdit demonstration for my next class. \:\)

As I just taught in my class yesterday.. a child process will inherit the environment of its parent. Thus, if you have any problems passing an argument to the child process via Kix2Exe or CPAU, you can define several environment variables (using SetL) before calling the child process. The child procecss will have COPIES of those variables. I emphasize COPIES because the child can modify their values without affecting the Parent environment - very much unlike the real world. ;\)

Not for the casual process, but - using the registry and storing a value in HKLM\Software\%USERDOMAIN%\appid:value is an alternative way of passing data. Using an INI file, with read/writeprofilestring() functions is also an option that's easy to implement and easier to clean up afterwards - just delete the file.

So, now you have a couple of ways to solve your problem.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D