>>I agree with this, but would like to add that it's perfectly ok to learn from the code that the form wizard uses, and steal ideas to put in your own classes.
>
>Erik,
>
>The classes used by the from wizard are NOT a good model to learn from at all.
>

Jim, the list of problems that I have with the wizard stuff is at least as long as your list of problems. But when you are at the stage of learning what SKIP does instead of how good OOP works, you steal from wherever you can. I had an EXTREMELY difficult time picking up the basics of Fox from the documentation, and examples and wizard code was the only thing that gave me anough jumpstart to get going.

Try something: pretend you don't know how to close a table (USE IN, or USE). Now go to the documentation and try to figure it out. Looking up "Close" gets you nowhere close, and you could spend an hour finding this. To be honest, I didn't figure it out for days, and just relied on CLOSE ALL when my program was finished.

I remember spending most of a day trying to figure out what "aliases" are. If you don't have someone to tell you, and don't have examples to work from these simple things can truly make a molehill look like a mountain.

The wizard code and the tastrade/solutions apps are the most accessible samples for a beginner. All of them are fatally flawed from a design standpoint, but have code in them that gets the job done, which is what a beginner needs to know. Sure, you could point them at the free CodeBook framework, but then they would NEVER learn the basics, and probably have dreams that night about oceans of code.