>Right. Sometimes it's just easier if you can look at a program file. It wouldn't be very difficult to pull all of the procedures from a VCX or SCX file and then edit them and push them back into the appropriate file, but it isn't very automated. You would have to make sure that you always remembered to put it back when you were done, which could lead to problems. I guess it is a fundamental design difference between something like Delphi and VFP. Delphi just stores everything in a text file and parses it, while VFP stores it in a table.

Writing an utility which would generate code from .scx and into a .prg and vice versa is not that impossible - I think there are utilities like PrgToVcx (check the files section, I think there's something of the kind there), but there's another obstacle.

In order to have .prg code completely emulate an equivalent .scx, it would have to have local subclasses for any objects within containers, because you can't just have a Define Class with methods for objects which are not immediate children of a form (or a formset). It would take lots of local subclassing for each object which is deeper than one level down the containership hierarchy, and I have some serious doubts on the overall readability of such code, and of the possibility that it may be directly transportable back to .scx after all of subclassing.