>OK, Harry, each to his own way (...out of mind... know the rest?). There may be some speed issues here (VFP needs to parse those hundred names each time instead of looking directly into the .app or .exe), but they may be neglectable, and some memory issues (loading the whole procedure file with hundreds of functions where you only use a dozen), which are also neglectable on today's machines.

exactly.

>
>Though, I think you either have nice sets of similar functions there, if you can do a global search & replace just like that. I've had such a set of couple of hundreds of routines (each in a separate .prg) and I never had to edit more than two or three at a time. They're all doing their jobs happily unaware of each other, unless they call each other, but then they talk through their parameters. Can't remember the last time I did any sort of global search/replace... maybe five years ago, when I was inventing my own naming convention within these functions, to avoid stumbling over public or outer private vars.

oh I'm not claiming this is state of the art programming: the project goes back 10 years so its got a lot of dead wood in it.
>
>Still, doing a global search/replace on dozens of files worked fine in Filer. Don't you miss Ctrl+F, enter parameters, Ctrl+W to close the dialog, Ctrl+E to >open all tagged files, eh?

the days when men were men, women were women and little green furry things from alpha centauri were little green furry things...

Harry