Hi Mike,

Ok, now I have two your very respectful opinions to keep these functions into separate files. My only contrpoint (? how I should spell?) is that some of these functions are very small (few lines of code) and the number of functions is too big (~500-600)...
But may be both of you're right. Since I haven't started this application yet (have another one to do, besides all other stuff), right now I'm just collecting ideas :)

I had a thread several months ago about advantages and disadvantages of using one big procedure file vs. bunch of small functions. As far as I recall, the latest approach is preferrable. I have to find this thread...

Thanks for your ideas, Mike & Ed & Barbara & Paul Vlad

>Hi Nadya
>
>I have to agree with Ed. If you keep functions in separate files, you would only need to know the name of the function in order to edit it. You could copy the code to a temporary cursor with a memo field and use an edit box to edit it. Save the memo field back as a file ... recompile ONLY THE CHANGED .prg instead of the entire procedure file (which is faster!). Further, you can edit these and recompile them outside of your app more easily. You'd have to keep these .PRGs outside of the main .EXE file., but you must be doing that to the procedure file now.
>
>Hope that helps.