Hi Michel

I had a similar problem using execscript. The code in my scripts needed to set classlib to, but when the exe was built, the scripts could not find the vcx. The solution evolved from discussions here on the UT!

What I ended up doing was attempting a regular SET CLASSLIB TO, but failing that, looking at the calling stack (SYS(16,0)) for an EXE and doing a SET CLASSLIB TO in that EXE.

>>well, i am starting the guessing game now, but if i understand you right your root .exe is calling other (secondary) .exe's. if this is the case, i don't think that the secondary .exe knows what the root .exe did in matters of 'set classlib...'. therefor the seconday .exe has to search for the .vcx in all the different path's.
>
>Ok, that makes sense. So, first, it's still a mystery as to know why this is working on our production server where no VCX are stored anywhere. Secondly, how would I go to be safer in order to have those secondary EXE to see the classlib definitions which are loaded in the root?