>Hi Jet,
>
>I strongly recommend to you to keep away from code generators.
>They will not do any good to you. Create set of classes that can handle your way of thinking and doing things.
>
>I am using my class generators just to set properties to next generation of base business and gui objects because I am as lazy as one can be creating subclasses and setting properties manualy.

Same here. Code generators belong to DOS world - back then, they saved me a lot of time. I wrote a set of generator which allowed me to build a simple application (one entry form, one report, menu, metadata tables) out of a single table within minutes. Which was all good and great when a GET field had about two or three properties (when, valid, picture... anything else?).

Now since we've gone visual I'm still having some code generating stuff, but - it just builds a start for me. Sets some properties, generates some methods in the bizobject (which is in a prg) and that's it. From that point on, it's all manual putting of objects on a form/class, writing code... with a lot of intellisense macros, my own builders. If ever I think I need some code generated and inserted into a series of objects, then I stop and rethink their classes. Do I need a subclass here? What would the parameters be? Can I use BindEvents() instead?

So yes, I still generate some code and programmatically create some visual classes - the parts which are the same everywhere but can be derived from the form's main table. But that's just a skeleton. From there on, it's all coding as usual.