With Visual FoxPro 3.0, when you find yourself saying, "I could do it in 2.6 by modifying GENSCRN or using GENSCRNX," this should be an indication for you to start thinking about a class hierarchy to solve the problem using object-orientation. There is no reason for code generation with Visual FoxPro since it is now an object-oriented language. You can build classes and class relationships that allow you the same flexibility as FoxPro 2.x code generation (SPR) but with the power of encapsulation, polymorphism, and inheritance.