Hi Dragan,

Thanks for detailing your findings as they confirm what I thought might be going on. I think your conclusion is probably the right one. The other responder to this thread (Charles) gives his workaround to this problem and then my response to him "muses" a bit about what the effect of using SET PROCEDURE might be to solving it.

Albert

>
>No, but I once had an equivalent problem: a .frx file called a form from within its .dataenvironment.init - and the following didn't work:
>- report outside project, form inside, its classlib inside
>- report outside project, form outside, its classlib inside
>
>What eventually worked, was
>- report outside project, form outside, its classlib outside
>- report outside project, form outside based on Fox base classes
>- everything inside project.
>
>The first two didn't work even when we tried to use newobject() with the third parameter to create the form from its class (trying to skip the .scx). This was in VFP6 SP3, I think, maybe SP5.
>
>The conclusion I got from this is if you're running anything from outside the .exe and the .vcxes are inside the .exe, the outside code is marooned and can't find almost any of the stuff which is inside the .exe. IOW, bad news for you, unless someone sheds some light on the problem and comes up with the right way to do this.