>Hi Mike
>
>I've spent years trying to convince people to not use procedure files. They are usually an arbitrary collection of barely related things. I believe the set procedure command was originally a work around to allow longer procedure names than 8 char file names.
>
>In your case, having a routine buried in a procedure file is preventing you from executing it the way you want. If you would extract that routine from the procedure file, add it to the project as a separate .prg file and rebuild your exe, you will still be able to execute it in the current exe and you will be able to execute it from an external exe via DO prgname IN exename.

Hi,

I think so it was just about generate one application file for run with old Foxbase runtime edition. You were creating a procedure file with Foxbind.exe, compile it and run with Foxbase runtime .EXE (I can't remember it's name).