Hello John,

>We still have this thing here about doing most things in PRGs.

Although I like using classes, OOP, etc., I'm still prefer using prg files where appropriate, although these days I use them as procedure files containing lots of functions, procedures, etc., instead of having hundreds of little .prg files cluttering-up the place. Every application of mine has two procedure files loaded - ProcComm.prg (common/generic routines that can be used in any application) and ProcApp.prg (application-specific routines).


>Mostly because you can have debug on and not have all your source code in the compiled EXE...

Personally I never debug from a compiled .exe or .app, unless there is a problem I cannot reproduce in my development environment. I always develop and debug directly from the source code. As long as the path includes all form, class library, program, menu, etc. files, you can watch/suspend/fix the source directly without the need for so many .prg files.

>...and because the VFP editor is so weak

I have to disagree with you there. Sure it lacks some features found in other editors (TextPad is my favourite at present), but when developing in VFP it can do many things that other editors cannot.

> (unless you are addicted to IntelliSense).

Not me! I have it switched-off. Maybe I haven't spent enough time with it to customise it to my advantage, but I don't like it at all. It gets in the way and I find it more of a hinderence than a help. I can understand it being useful for beginners, though.


Regards,
Alan