> I worked for a company in 1999 which used to sell a fairly complex application in VFP 6. I was a bit surprised to learn that they did not use Visual Form designers. All forms were coded as classes written as PRGs. The forms were quite complex as these included pageframes, listboxes and grids. When I asked the same question -- "Why can't we use Form designer?", they game me two reasons:
>
> 1. Forms coded as prg load and run faster.That may have been true in early versions of VFP but the issues were in VFP 3.0 and V5.0 - they were fixed in VFP 6.0 and I am pretty sure that there is no significant difference nowadays.
> 2. As code for all methods is at one place, it is easier to debug and maintain methods. HOw is it easier to debug and maintain 25000 lines of code in a single PRG than 250 x 100 line mnethods, individually named and selectable through the designer?
YOu can open multiple code windows and have different methods in different windows! Hard to do that in a PRG - especially a large one.
These are just non-sense reasons! Probably the truth is that the originator of the code didn't know how to use the designers efficiently and copied the code from a FP2.x => VFP 3.0 converter!
Regards
Andy Kramek
Microsoft MVP (Visual FoxPro)
Tightline Computers Inc, Akron Ohio, USA