Hi Anita ---

Well, there is DO procedure IN procfile. As to the rest of your suggestion, I would doubt it. Current design theory for VFP suggests that you're better off creating function or domain specific custom classes and creating methods in those classes to call. Something like:

oDB=NEWOBJECT("datafuncs","myclasslib")
oDB.GetTotals()
oDB.Reindex()




>Just a thought!
>
>Is there anything under MS's consideration for simplifying
>"set procedure to "
>
> something similar to NewObject()
>
>or a new way of calling functions without set procedure to.
>
>May be somthing like:
>***
>Function function_name( [p1, [p2, [...]]])in program_or_library_name
>***
>
>and let FoxPro take care of activating and releasing of programs.