>>Thank You Jason,
>>
>>But I think it cannot be pathing problem. It happens also, when I am working with only one EXE built according to the framework's manual. In this case I have included all vcx into EXE.
>>It is crazy, but the same code is normali functioning when compiled with MM version 6.0
>>
>>Good weekend,
>>
>>Josef
>
>I have an idea... surprising, huh? I know there was a problem with the 6.0 framework identifying the wrong exe as the one to SET CLASSLIB IN. It had to do with using SYS(16) to determine which was the calling program. Anyway, to make a long story slightly longer, Kevin changed some code (in MMortals\Common30\Progs\Setup.prg... SetProcsAndLibs() is the method) that used to issue a SET CLASSLIB IN. Now it calls SET CLASSLIB without the IN. This may be causing your problem, because it won't recognize where the classes are... unless they're in the same path as the executable/app
>
>You may have luck in copying the old Setup.prg into your new MMortals directory (of course, copy the old one to a new name/directory first!) and then recompiling.
>-Hope that helps!
>---J

Dear Jason!

Your idea was genious!!!!

I have changed code in Setup.prg SetProcAndLibs() to old code from MM6.0 and reports start to function! This problem was not onla in case when libraries were in different EXEs, but olso in case when application was compiled in one exe.

Thank you very much

Josef