>>Dear Jason,
>>
>>Exactly, when report is included in the APP or EXE it works, and when report is not included in EXE it fails to find the classes, referred to in the report's methods. Thouse classes exist in the main application (EXE, when I use only one EXE. Or they exist in several EXEs (by the modular structure) - in this case I use abstarct factory and classes.dbf to map them.
>>
>>When I put thouse classes in the main directotry - reports find them.
>>
>>Josef
>
>Check classes.dbf and make sure you have the cLibrary and cFileName entered correctly for each of your libraries in the separate EXEs you mentioned.
>
>It appears to me you have a pathing problem. When you include the file, SetProcsAndLibs() automatically adds the path to the SET CLASSLIB, so you shouldn't have a problem. However, when you don't include the vcx, you're either relying on it being in the main path (the first place FoxPro "looks" when it can't find something on its own) or you're relying on the abstract factory, which, in turn relies on Classes.dbf.... so that's where I'd look first.
>Good luck...
>---J

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