>Hi,
>
>Say I have a function that I want to put into a separate PRG file. I can do it without declaring the FUNCTION FunctName within the PRG file. And then call this PRG name as a function. E.g.
>

>do MyPrgName with tParam1, tParam2
>

>
>If I add a FUNCTION FuncName then I would have to do SET PROCEDURE to MyPrgMane ADDITIVE (somewhere at the top of the app) and then call it as
>

>FuncName( tParam1, tParam2)
>

>
>What are the advantages or disadvantages of having the function inside a PRG without the FUNCTION declaration?

Look up the order FP (/ VFP) is looking for a function. Back in the stone age just looking in the current .prg could give you speed benefits, but that difference on todays machines and if compiled into an app/exe is not a deciding factor.

IMO Mikes position to always put each function in separate prg and trust the compiling step is not a easy to manage as several functions usually needed together for a similar topic (CSV list behaviour for instance) in a separate prg added wit set proc addi