>>>>Yes, I plan to remove this function from the procedure file and leave in SP.
>One of the few real backdrops of vfp compared to FPW is the handling of identically
>named functions. There even was a warning [at least in the help files of vfp6,
>haven't checked recently] to avoid having functions with the same name,
>since calling behaviour [at least across different loaded apps]
>depends in some cases on the actions the user has taken previously.
>
>>=MyFunction(par,par) or DO myFunction with ... to make internal search quicker?
>Remember that they are NOT equivalent in the "naive" form as parameters are
>passed by ref with DO. I personally prefer style 1, but style 2 is the only way
>to call IN [prg,app,exe] which can be helpful in large legacy programs.
>
>regds
>
>thomas
Thanks for your thoughts. I like the syntax 1 and almost never use syntax 2.
If it's not broken, fix it until it is.
My Blog