Hi!

OurApp.EXE contains a lot of class definitions that could not be found when you use set procedure to. This is because PRG files in EXE could contain DEFINE CLASS statamenet that access custom classes that are not loaded into memory at the moment you use that command. This is just my siggestion. We never use SET PROCEDURE TO ...EXE, we always set up propcedure files by PRG name, and issue SET PROCEDURE TO ... as many times as required.

As about class library - we load all class libraries at the application start. So no need to do SET CLASSLIB in the form load methods. Once libraries are loaded in the memory, they are visible for all external module calls.

There are bugs in the VFP related to setting the class libraries and procedure files from one EXE to another, I guess the same problem happens when you use FXP file.

HTH.

>To All,
>Our framework classes are in the application EXE and obviously any Program/Form in the EXE runs fine. The aplication provides a hook to enable running of any .FXP that may not be in the EXE. It simply has to reside in the same folder as the EXE. The arrangement works fine if the external program has no call to a form that uses any of our framework classes. Forms using Foxpro baseclasses work fine (This is because Foxpro Runtime DLL is included in the Seup Wizard that manages the EXE). I have tried the following in Form.Load() as well as in the Program that calls the form(even though the form's in Private DataSession)
>
>Set Procedure to OurApp.EXE
>SET Classlib to Ourclass.vcx
>
>Yet I keep getting "Class Not Found Error"
>
>Can anyone tell me what else I can do ?
>
>TIA,
>
>Nitin