I advise you consider not making a .PRG a library of functionality. You can then have a path to your shared prgs and call any of the functions without SET PROCEDURE TO, just as you can call any VFP function.

>Thanks Hilmar.
>Gerard
>
>>>Hi.
>>>I have a no. of different apps , all in different folders, but I want to use some .prg's in a shared folder.
>>>
>>>Say my shared folder is c:\MysharedFolder
>>>
>>>What is the best way to set up my individual apps , to look in the shared folders ?. If I Set procdure to c:\MySharedFolder\MySahredPrg1, will this cause a problem in running the app because It does not exist at run time.
>>>The same applied to Set ClassLib
>>>regards,
>>>Gerard
>>
>>I tried shared PRGs and classes, and it turns out that can cause trouble with defined constants - which of course may have different value for different applications. Such constants might include #APPLICATION_CAPTION, and other application-specific stuff. Switching from one application to another would imply: (a) overwriting the appropriate .h files, and (b) recompiling.
>>
>>Anyway, your SET PROCEDURE to c:\... should NOT cause a problem, 'cause the PRGs and VCXs are normally included within the EXE. VFP will look in the EXE first, and the specific folder is not needed, AFAIK.