>>I have a function (fairly small) that loads a cursor from XML (application configuration values). This
>>function can be in the main application .PRG or in some other MISC_FUNC.PRG (loaded in the
>>main .PRG via SET PROCEDURE TO MISC_FUNC ADDITIVE). Does it matter for the speed of
>>the program is this function in one place or the other? Any other things to consider as far as
>>the place for this function?
>>TIA
>
>
>To my knowledge it doesn't matter any longer. If you have the ability to build a .EXE or .APP file, then you can include it in the project in any form and Visual FoxPro will resolve for itself at compile time where it is and how it will be called. It is a common practice to have all related functions in a single PRG as separate PROCEDURE or FUNCTIONs within, but it is not required. I personally like to have a single large PRG (or several) which contain related functions as are used, and then use SET PROCEDURE TO name.prg ADDITIVE for each one. Visual FoxPro resolves everything automatically in that way, and there are only a few disk files to sift through to find something.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
