The Class Browser can produce bogus code (ADD OBJECT form1.grdfoo.column1.header1 AS header) with the View Source option, so the resulting source may need modification.

Dave

>>I would like to maintain/view all code in one prg instead of using the editing method inside the form which I can't jump back/and forth with a place
>
>You can code all of your classes and forms in a .PRG file, you just have to give up on usoing the Visual Tools to maintain the code - no drag and drop, etc for creating and maintaining the form, just like you could hand-code screens in FPDOS/FPW. The use of the non-visual environment is entirely feasible; some classes can't be subclassed except through programmatic means (subclassing the Session object is one example).
>
>If you have a form now and would like to maintain it as code, you can always open the form with the Class Browser and use that to save the form and all it's component objects in source code through the View Source option. Once exported as source, there's no convenient way of going back to the visual development environment.