>>>Well, I tried to implement the plan A. I get the latest version from VSS, but now I'm having the same problem as I had before. I had to try another plan.
>>
>>Didn't you say "last good version from VSS"?
>>
>>But really, what's the problem? You're trying to get help with the way you want to solve it, but we still don't know what's the problem, except that it's something about the datasession.
>
>Dragan,
>
>I traced the problem in the builder. It's an error 1733 when it tries to instantiate a class using CREATEOBJECT command. The classlib is supposed to be in the memory, but it is not. I checked SET('classlib'), it's a very very long string:

[snip]

>but aBatchProcessBiz library is not here. Trying SET CLASSLIB to aBatchProcessBiz additive didn't help.
>
>However, a second ago I tried SET CLASSLIB TO
>=setx()
>set classlib to aBatchProcessBiz.vcx additive and then createobject, it seems to work. I think, we may hit some limit...
>
>The length of the SET('classlib') is 5450. I'm not sure how setx() works, I need to check its code. I want to work with different project right now, but it seems like it is taking libraries from MMVisCollect project rahter than from BatchProcess project.

Just set a breakpoint in SetX (I assume that's the place where it does all the Set Library/Procedure, and try to see how does it pick the pjx file from which it reads the list of classlibs and procedures. Probably you need to set the current project somewhere in metadata.