Tore,
thanks for the tip on MutiEdit. I will try the free 30 trial and see how it compaires. The thing I miss the most when I have to use the VFP edit is the column cut/copy and paste. We use that a lot around here.


>To Brief, or not to Brief, that's the question...
>
>Personally I used Brief for many years, until I switched to MultiEdit about 10 years ago. MultiEdit is far superior to Brief, and is configurable, one of the modes is Brief mode. Read more about MultiEdit at www.multiedit.com, together with Evolve, which I believe now is included, you will throw way Brief tomorrow!
>
>However, I now only use MultiEdit for HTML, I have larnt to love the VFP editor, and especially with Intellisense, I find the VFP editor superb. But, it's a matter of taste.
>
>>Tore,
>>thanks for the info. I was kind of leaning that way but wanted to get other peoples opinons. As for editing the files, we don't use the VFP editor except when working in forms or if we need the Intellisense. We use an old DOS editor, Brief. It has so many features it just blows away the VFP editor and is 10 times faster for program editing.
>>John.
>>
>>>Hi John,
>>>
>>>Having many procedures in one file gives better performance. Regarding function 32 at line 6532, why don't you use Document View from the Tools menu?
>>>
>>>>Does anyone have any idea if there is any perfomance difference between putting many programs in a procedure file or just leaving them as seprate programs? We have two procedure files. One holds all the general utilites such as converting number to words for checks, etc. The other is specific to each system and holds things like validating invoice numbers, etc. These files have become large even though we only put mostly small functions in them and this causes them to become hard to maintain. Getting to the 32nd function that starts on line 6532 can be a pain after a while.