>Thank you. My problem has never been the speed, neither compiling no at run-time. Mike assumed I was "after speed."
>The downside - for me - to place each function/procedure in a separate .PRG is a maintenance headache. I have not counted but the application probably has a couple of hundred procedures. And having to scroll through this list in the project manager (if necessary to look at the code of whatever), would increase the time of maintenance. I know many will say that instead of the Functions/Procedures I should have them in classes. And maybe so. But I started this application way before I knew anything about how to build classes. When I can and when it makes sense, I do refactor the code.

Hi Dmitry,

I haven't read through the whole thread yet, but yesterday I saw Doug's post about sharing VFox conference content. The first session I opened was by Jody M (if I remember right) about SQL Server Query Plans and lots of stuff behind the scenes. It was a very good session (I put it in the background while working, but I liked it). The next one is by Doug himself about new Project Explorer. I haven't listened to this one but it sounds like a very cool new tool which should replace Project Manager. If you do lots of VFP development, I suggest to take a moment to go to this session and grab the tool.